Base station configuration sharing in a wireless network

ABSTRACT

A base station distributed unit receives at least one message from a first base station central unit. The at least one message comprises one or more first configuration parameters associated with the first base station central unit. The at least one message comprises one or more second configuration parameters associated with a second base station central unit. The base station distributed unit transmits the one or more first configuration parameters and the one or more second configuration parameters.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of International Application No.PCT/US2019/036530, filed Jun. 11, 2019, which claims the benefit of U.S.Provisional Application No. 62/683,373, filed Jun. 11, 2018, and U.S.Provisional Application No. 62/696,912, filed Jul. 12, 2018, which arehereby incorporated by reference in their entirety.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

Examples of several of the various embodiments of the present disclosureare described herein with reference to the drawings.

FIG. 1 is a diagram of an example RAN architecture as per an aspect ofan embodiment of the present disclosure.

FIG. 2A is a diagram of an example user plane protocol stack as per anaspect of an embodiment of the present disclosure.

FIG. 2B is a diagram of an example control plane protocol stack as peran aspect of an embodiment of the present disclosure.

FIG. 3 is a diagram of an example wireless device and two base stationsas per an aspect of an embodiment of the present disclosure.

FIG. 4A, FIG. 4B, FIG. 4C and FIG. 4D are example diagrams for uplinkand downlink signal transmission as per an aspect of an embodiment ofthe present disclosure.

FIG. 5A is a diagram of an example uplink channel mapping and exampleuplink physical signals as per an aspect of an embodiment of the presentdisclosure.

FIG. 5B is a diagram of an example downlink channel mapping and exampledownlink physical signals as per an aspect of an embodiment of thepresent disclosure.

FIG. 6 is a diagram depicting an example frame structure as per anaspect of an embodiment of the present disclosure.

FIG. 7A and FIG. 7B are diagrams depicting example sets of OFDMsubcarriers as per an aspect of an embodiment of the present disclosure.

FIG. 8 is a diagram depicting example OFDM radio resources as per anaspect of an embodiment of the present disclosure.

FIG. 9A is a diagram depicting an example CSI-RS and/or SS blocktransmission in a multi-beam system.

FIG. 9B is a diagram depicting an example downlink beam managementprocedure as per an aspect of an embodiment of the present disclosure.

FIG. 10 is an example diagram of configured BWPs as per an aspect of anembodiment of the present disclosure.

FIG. 11A, and FIG. 11B are diagrams of an example multi connectivity asper an aspect of an embodiment of the present disclosure.

FIG. 12 is a diagram of an example random access procedure as per anaspect of an embodiment of the present disclosure.

FIG. 13 is a structure of example MAC entities as per an aspect of anembodiment of the present disclosure.

FIG. 14 is a diagram of an example RAN architecture as per an aspect ofan embodiment of the present disclosure.

FIG. 15 is a diagram of example RRC states as per an aspect of anembodiment of the present disclosure.

FIG. 16 is an example diagram of an aspect of an embodiment of thepresent disclosure.

FIG. 17 is an example diagram of an aspect of an embodiment of thepresent disclosure.

FIG. 18 is an example diagram of an aspect of an embodiment of thepresent disclosure.

FIG. 19 is an example diagram of an aspect of an embodiment of thepresent disclosure.

FIG. 20 is an example diagram of an aspect of an embodiment of thepresent disclosure.

FIG. 21 is an example diagram illustrating a legacy base station sharingnetwork architecture.

FIG. 22 is an example diagram of an aspect of an embodiment of thepresent disclosure.

FIG. 23 is an example diagram of an aspect of an embodiment of thepresent disclosure.

FIG. 24 is an example diagram of an aspect of an embodiment of thepresent disclosure.

FIG. 25 is an example diagram of an aspect of an embodiment of thepresent disclosure.

FIG. 26 is an example diagram of an aspect of an embodiment of thepresent disclosure.

FIG. 27 is an example diagram of an aspect of an embodiment of thepresent disclosure.

FIG. 28 is an example diagram of an aspect of an embodiment of thepresent disclosure.

FIG. 29 is an example diagram of an aspect of an embodiment of thepresent disclosure.

FIG. 30 is an example diagram of an aspect of an embodiment of thepresent disclosure.

FIG. 31 is an example diagram of an aspect of an embodiment of thepresent disclosure.

FIG. 32 is an example diagram of an aspect of an embodiment of thepresent disclosure.

FIG. 33 is an example diagram of an aspect of an embodiment of thepresent disclosure.

FIG. 34 is an example diagram of an aspect of an embodiment of thepresent disclosure.

FIG. 35 is an example diagram of an aspect of an embodiment of thepresent disclosure.

FIG. 36 is an example diagram of an aspect of an embodiment of thepresent disclosure.

FIG. 37 is an example diagram of an aspect of an embodiment of thepresent disclosure.

FIG. 38 is an example diagram of an aspect of an embodiment of thepresent disclosure.

FIG. 39 is an example diagram of an aspect of an embodiment of thepresent disclosure.

FIG. 40 is an example diagram of an aspect of an embodiment of thepresent disclosure.

FIG. 41 is an example diagram of an aspect of an embodiment of thepresent disclosure.

FIG. 42 is an example diagram of an aspect of an embodiment of thepresent disclosure.

FIG. 43 is an diagram of an aspect of an example embodiment of thepresent disclosure.

FIG. 44 is an diagram of an aspect of an example embodiment of thepresent disclosure.

FIG. 45 is an diagram of an aspect of an example embodiment of thepresent disclosure.

FIG. 46 is an diagram of an aspect of an example embodiment of thepresent disclosure.

FIG. 47 is an diagram of an aspect of an example embodiment of thepresent disclosure.

FIG. 48 is an diagram of an aspect of an example embodiment of thepresent disclosure.

FIG. 49 is an diagram of an aspect of an example embodiment of thepresent disclosure.

FIG. 50 is an diagram of an aspect of an example embodiment of thepresent disclosure.

FIG. 51 is an diagram of an aspect of an example embodiment of thepresent disclosure.

FIG. 52 is an diagram of an aspect of an example embodiment of thepresent disclosure.

FIG. 53 is an diagram of an aspect of an example embodiment of thepresent disclosure.

FIG. 54 is an diagram of an aspect of an example embodiment of thepresent disclosure.

FIG. 55 is an diagram of an aspect of an example embodiment of thepresent disclosure.

DETAILED DESCRIPTION OF EMBODIMENTS

Example embodiments of the present disclosure enable operation ofwireless systems. Embodiments of the technology disclosed herein may beemployed in the technical field of multicarrier communication systems.More particularly, the embodiments of the technology disclosed hereinmay relate to radio access technologies in multicarrier communicationsystems.

The following Acronyms are used throughout the present disclosure:

-   -   3GPP 3rd Generation Partnership Project    -   5GC 5G Core Network    -   ACK Acknowledgement    -   AMF Access and Mobility Management Function    -   ARQ Automatic Repeat Request    -   AS Access Stratum    -   ASIC Application-Specific Integrated Circuit    -   BA Bandwidth Adaptation    -   BCCH Broadcast Control Channel    -   BCH Broadcast Channel    -   BPSK Binary Phase Shift Keying    -   BWP Bandwidth Part    -   CA Carrier Aggregation    -   CC Component Carrier    -   CCCH Common Control CHannel    -   CDMA Code Division Multiple Access    -   CN Core Network    -   CP Cyclic Prefix    -   CP-OFDM Cyclic Prefix-Orthogonal Frequency Division Multiplex    -   C-RNTI Cell-Radio Network Temporary Identifier    -   CS Configured Scheduling    -   CSI Channel State Information    -   CSI-RS Channel State Information-Reference Signal    -   CQI Channel Quality Indicator    -   CSS Common Search Space    -   CU Central Unit    -   DC Dual Connectivity    -   DCCH Dedicated Control CHannel    -   DCI Downlink Control Information    -   DL Downlink    -   DL-SCH Downlink Shared CHannel    -   DM-RS DeModulation Reference Signal    -   DRB Data Radio Bearer    -   DRX Discontinuous Reception    -   DTCH Dedicated Traffic CHannel    -   DU Distributed Unit    -   EPC Evolved Packet Core    -   E-UTRA Evolved UMTS Terrestrial Radio Access    -   E-UTRAN Evolved-Universal Terrestrial Radio Access Network    -   FDD Frequency Division Duplex    -   FPGA Field Programmable Gate Arrays    -   F1-C F1-Control plane    -   F1-U F1-User plane    -   gNB next generation Node B    -   HARQ Hybrid Automatic Repeat reQuest    -   HDL Hardware Description Languages    -   IE Information Element    -   IP Internet Protocol    -   LCID Logical Channel IDentifier    -   LTE Long Term Evolution    -   MAC Media Access Control    -   MCG Master Cell Group    -   MCS Modulation and Coding Scheme    -   MeNB Master evolved Node B    -   MIB Master Information Block    -   MME Mobility Management Entity    -   MN Master Node    -   NACK Negative Acknowledgement    -   NAS Non-Access Stratum    -   NG CP Next Generation Control Plane    -   NGC Next Generation Core    -   NG-C NG-Control plane    -   ng-eNB next generation evolved Node B    -   NG-U NG-User plane    -   NR New Radio    -   NR MAC New Radio MAC    -   NR PDCP New Radio PDCP    -   NR PHY New Radio PHYsical    -   NR RLC New Radio RLC    -   NR RRC New Radio RRC    -   NSSAI Network Slice Selection Assistance Information    -   O&M Operation and Maintenance    -   OFDM Orthogonal Frequency Division Multiplexing    -   PBCH Physical Broadcast CHannel    -   PCC Primary Component Carrier    -   PCCH Paging Control CHannel    -   PCell Primary Cell    -   PCH Paging CHannel    -   PDCCH Physical Downlink Control CHannel    -   PDCP Packet Data Convergence Protocol    -   PDSCH Physical Downlink Shared CHannel    -   PDU Protocol Data Unit    -   PHICH Physical HARQ Indicator CHannel    -   PHY PHYsical    -   PLMN Public Land Mobile Network    -   PMI Precoding Matrix Indicator    -   PRACH Physical Random Access CHannel    -   PRB Physical Resource Block    -   PSCell Primary Secondary Cell    -   PSS Primary Synchronization Signal    -   pTAG primary Timing Advance Group    -   PT-RS Phase Tracking Reference Signal    -   PUCCH Physical Uplink Control CHannel    -   PUSCH Physical Uplink Shared CHannel    -   QAM Quadrature Amplitude Modulation    -   QFI Quality of Service Indicator    -   QoS Quality of Service    -   QPSK Quadrature Phase Shift Keying    -   RA Random Access    -   RACH Random Access CHannel    -   RAN Radio Access Network    -   RAT Radio Access Technology    -   RA-RNTI Random Access-Radio Network Temporary Identifier    -   RB Resource Blocks    -   RBG Resource Block Groups    -   RI Rank Indicator    -   RLC Radio Link Control    -   RRC Radio Resource Control    -   RS Reference Signal    -   RSRP Reference Signal Received Power    -   SCC Secondary Component Carrier    -   SCell Secondary Cell    -   SCG Secondary Cell Group    -   SC-FDMA Single Carrier-Frequency Division Multiple Access    -   SDAP Service Data Adaptation Protocol    -   SDU Service Data Unit    -   SeNB Secondary evolved Node B    -   SFN System Frame Number    -   S-GW Serving GateWay    -   SI System Information    -   SIB System Information Block    -   SMF Session Management Function    -   SN Secondary Node    -   SpCell Special Cell    -   SRB Signaling Radio Bearer    -   SRS Sounding Reference Signal    -   SS Synchronization Signal    -   SSS Secondary Synchronization Signal    -   sTAG secondary Timing Advance Group    -   TA Timing Advance    -   TAG Timing Advance Group    -   TAI Tracking Area Identifier    -   TAT Time Alignment Timer    -   TB Transport Block    -   TC-RNTI Temporary Cell-Radio Network Temporary Identifier    -   TDD Time Division Duplex    -   TDMA Time Division Multiple Access    -   TTI Transmission Time Interval    -   UCI Uplink Control Information    -   UE User Equipment    -   UL Uplink    -   UL-SCH Uplink Shared CHannel    -   UPF User Plane Function    -   UPGW User Plane Gateway    -   VHDL VHSIC Hardware Description Language    -   Xn-C Xn-Control plane    -   Xn-U Xn-User plane

Example embodiments of the disclosure may be implemented using variousphysical layer modulation and transmission mechanisms. Exampletransmission mechanisms may include, but are not limited to: CodeDivision Multiple Access (CDMA), Orthogonal Frequency Division MultipleAccess (OFDMA), Time Division Multiple Access (TDMA), Wavelettechnologies, and/or the like. Hybrid transmission mechanisms such asTDMA/CDMA, and OFDM/CDMA may also be employed. Various modulationschemes may be applied for signal transmission in the physical layer.Examples of modulation schemes include, but are not limited to: phase,amplitude, code, a combination of these, and/or the like. An exampleradio transmission method may implement Quadrature Amplitude Modulation(QAM) using Binary Phase Shift Keying (BPSK), Quadrature Phase ShiftKeying (QPSK), 16-QAM, 64-QAM, 256-QAM, and/or the like. Physical radiotransmission may be enhanced by dynamically or semi-dynamically changingthe modulation and coding scheme depending on transmission requirementsand radio conditions.

FIG. 1 is an example Radio Access Network (RAN) architecture as per anaspect of an embodiment of the present disclosure. As illustrated inthis example, a RAN node may be a next generation Node B (gNB) (e.g.120A, 120B) providing New Radio (NR) user plane and control planeprotocol terminations towards a first wireless device (e.g. 110A). In anexample, a RAN node may be a next generation evolved Node B (ng-eNB)(e.g. 124A, 124B), providing Evolved UMTS Terrestrial Radio Access(E-UTRA) user plane and control plane protocol terminations towards asecond wireless device (e.g. 110B). The first wireless device maycommunicate with a gNB over a Uu interface. The second wireless devicemay communicate with a ng-eNB over a Uu interface. In this disclosure,wireless device 110A and 110B are structurally similar to wirelessdevice 110. Base stations 120A and/or 120B may be structurally similarlyto base station 120. Base station 120 may comprise at least one of a gNB(e.g. 122A and/or 122B), ng-eNB (e.g. 124A and/or 124B), and or thelike.

A gNB or an ng-eNB may host functions such as: radio resource managementand scheduling, IP header compression, encryption and integrityprotection of data, selection of Access and Mobility Management Function(AMF) at User Equipment (UE) attachment, routing of user plane andcontrol plane data, connection setup and release, scheduling andtransmission of paging messages (originated from the AMF), schedulingand transmission of system broadcast information (originated from theAMF or Operation and Maintenance (O&M)), measurement and measurementreporting configuration, transport level packet marking in the uplink,session management, support of network slicing, Quality of Service (QoS)flow management and mapping to data radio bearers, support of UEs inRRC_INACTIVE state, distribution function for Non-Access Stratum (NAS)messages, RAN sharing, and dual connectivity or tight interworkingbetween NR and E-UTRA.

In an example, one or more gNBs and/or one or more ng-eNBs may beinterconnected with each other by means of Xn interface. A gNB or anng-eNB may be connected by means of NG interfaces to 5G Core Network(5GC). In an example, 5GC may comprise one or more AMF/User PlanFunction (UPF) functions (e.g. 130A or 130B). A gNB or an ng-eNB may beconnected to a UPF by means of an NG-User plane (NG-U) interface. TheNG-U interface may provide delivery (e.g. non-guaranteed delivery) ofuser plane Protocol Data Units (PDUs) between a RAN node and the UPF. AgNB or an ng-eNB may be connected to an AMF by means of an NG-Controlplane (NG-C) interface. The NG-C interface may provide, for example, NGinterface management, UE context management, UE mobility management,transport of NAS messages, paging, PDU session management, configurationtransfer and/or warning message transmission, combinations thereof,and/or the like.

In an example, a UPF may host functions such as anchor point forintra-/inter-Radio Access Technology (RAT) mobility (when applicable),external PDU session point of interconnect to data network, packetrouting and forwarding, packet inspection and user plane part of policyrule enforcement, traffic usage reporting, uplink classifier to supportrouting traffic flows to a data network, branching point to supportmulti-homed PDU session, QoS handling for user plane, e.g. packetfiltering, gating, Uplink (UL)/Downlink (DL) rate enforcement, uplinktraffic verification (e.g. Service Data Flow (SDF) to QoS flow mapping),downlink packet buffering and/or downlink data notification triggering.

In an example, an AMF may host functions such as NAS signalingtermination, NAS signaling security, Access Stratum (AS) securitycontrol, inter Core Network (CN) node signaling for mobility between3^(rd) Generation Partnership Project (3GPP) access networks, idle modeUE reachability (e.g., control and execution of paging retransmission),registration area management, support of intra-system and inter-systemmobility, access authentication, access authorization including check ofroaming rights, mobility management control (subscription and policies),support of network slicing and/or Session Management Function (SMF)selection.

FIG. 2A is an example user plane protocol stack, where Service DataAdaptation Protocol (SDAP) (e.g. 211 and 221), Packet Data ConvergenceProtocol (PDCP) (e.g. 212 and 222), Radio Link Control (RLC) (e.g. 213and 223) and Media Access Control (MAC) (e.g. 214 and 224) sublayers andPhysical (PHY) (e.g. 215 and 225) layer may be terminated in wirelessdevice (e.g. 110) and gNB (e.g. 120) on the network side. In an example,a PHY layer provides transport services to higher layers (e.g. MAC, RRC,etc.). In an example, services and functions of a MAC sublayer maycomprise mapping between logical channels and transport channels,multiplexing/demultiplexing of MAC Service Data Units (SDUs) belongingto one or different logical channels into/from Transport Blocks (TB s)delivered to/from the PHY layer, scheduling information reporting, errorcorrection through Hybrid Automatic Repeat request (HARQ) (e.g. one HARQentity per carrier in case of Carrier Aggregation (CA)), priorityhandling between UEs by means of dynamic scheduling, priority handlingbetween logical channels of one UE by means of logical channelprioritization, and/or padding. A MAC entity may support one or multiplenumerologies and/or transmission timings. In an example, mappingrestrictions in a logical channel prioritization may control whichnumerology and/or transmission timing a logical channel may use. In anexample, an RLC sublayer may supports transparent mode (TM),unacknowledged mode (UM) and acknowledged mode (AM) transmission modes.The RLC configuration may be per logical channel with no dependency onnumerologies and/or Transmission Time Interval (TTI) durations. In anexample, Automatic Repeat Request (ARQ) may operate on any of thenumerologies and/or TTI durations the logical channel is configuredwith. In an example, services and functions of the PDCP layer for theuser plane may comprise sequence numbering, header compression anddecompression, transfer of user data, reordering and duplicatedetection, PDCP PDU routing (e.g. in case of split bearers),retransmission of PDCP SDUs, ciphering, deciphering and integrityprotection, PDCP SDU discard, PDCP re-establishment and data recoveryfor RLC AM, and/or duplication of PDCP PDUs. In an example, services andfunctions of SDAP may comprise mapping between a QoS flow and a dataradio bearer. In an example, services and functions of SDAP may comprisemapping Quality of Service Indicator (QFI) in DL and UL packets. In anexample, a protocol entity of SDAP may be configured for an individualPDU session.

FIG. 2B is an example control plane protocol stack where PDCP (e.g. 233and 242), RLC (e.g. 234 and 243) and MAC (e.g. 235 and 244) sublayersand PHY (e.g. 236 and 245) layer may be terminated in wireless device(e.g. 110) and gNB (e.g. 120) on a network side and perform service andfunctions described above. In an example, RRC (e.g. 232 and 241) may beterminated in a wireless device and a gNB on a network side. In anexample, services and functions of RRC may comprise broadcast of systeminformation related to AS and NAS, paging initiated by 5GC or RAN,establishment, maintenance and release of an RRC connection between theUE and RAN, security functions including key management, establishment,configuration, maintenance and release of Signaling Radio Bearers (SRBs)and Data Radio Bearers (DRBs), mobility functions, QoS managementfunctions, UE measurement reporting and control of the reporting,detection of and recovery from radio link failure, and/or NAS messagetransfer to/from NAS from/to a UE. In an example, NAS control protocol(e.g. 231 and 251) may be terminated in the wireless device and AMF(e.g. 130) on a network side and may perform functions such asauthentication, mobility management between a UE and a AMF for 3GPPaccess and non-3GPP access, and session management between a UE and aSMF for 3GPP access and non-3GPP access.

In an example, a base station may configure a plurality of logicalchannels for a wireless device. A logical channel in the plurality oflogical channels may correspond to a radio bearer and the radio bearermay be associated with a QoS requirement. In an example, a base stationmay configure a logical channel to be mapped to one or moreTTIs/numerologies in a plurality of TTIs/numerologies. The wirelessdevice may receive a Downlink Control Information (DCI) via PhysicalDownlink Control CHannel (PDCCH) indicating an uplink grant. In anexample, the uplink grant may be for a first TTI/numerology and mayindicate uplink resources for transmission of a transport block. Thebase station may configure each logical channel in the plurality oflogical channels with one or more parameters to be used by a logicalchannel prioritization procedure at the MAC layer of the wirelessdevice. The one or more parameters may comprise priority, prioritizedbit rate, etc. A logical channel in the plurality of logical channelsmay correspond to one or more buffers comprising data associated withthe logical channel. The logical channel prioritization procedure mayallocate the uplink resources to one or more first logical channels inthe plurality of logical channels and/or one or more MAC ControlElements (CEs). The one or more first logical channels may be mapped tothe first TTI/numerology. The MAC layer at the wireless device maymultiplex one or more MAC CEs and/or one or more MAC SDUs (e.g., logicalchannel) in a MAC PDU (e.g., transport block). In an example, the MACPDU may comprise a MAC header comprising a plurality of MAC sub-headers.A MAC sub-header in the plurality of MAC sub-headers may correspond to aMAC CE or a MAC SUD (logical channel) in the one or more MAC CEs and/orone or more MAC SDUs. In an example, a MAC CE or a logical channel maybe configured with a Logical Channel IDentifier (LCID). In an example,LCID for a logical channel or a MAC CE may be fixed/pre-configured. Inan example, LCID for a logical channel or MAC CE may be configured forthe wireless device by the base station. The MAC sub-headercorresponding to a MAC CE or a MAC SDU may comprise LCID associated withthe MAC CE or the MAC SDU.

In an example, a base station may activate and/or deactivate and/orimpact one or more processes (e.g., set values of one or more parametersof the one or more processes or start and/or stop one or more timers ofthe one or more processes) at the wireless device by employing one ormore MAC commands. The one or more MAC commands may comprise one or moreMAC control elements. In an example, the one or more processes maycomprise activation and/or deactivation of PDCP packet duplication forone or more radio bearers. The base station may transmit a MAC CEcomprising one or more fields, the values of the fields indicatingactivation and/or deactivation of PDCP duplication for the one or moreradio bearers. In an example, the one or more processes may compriseChannel State Information (CSI) transmission of on one or more cells.The base station may transmit one or more MAC CEs indicating activationand/or deactivation of the CSI transmission on the one or more cells. Inan example, the one or more processes may comprise activation ordeactivation of one or more secondary cells. In an example, the basestation may transmit a MA CE indicating activation or deactivation ofone or more secondary cells. In an example, the base station maytransmit one or more MAC CEs indicating starting and/or stopping one ormore Discontinuous Reception (DRX) timers at the wireless device. In anexample, the base station may transmit one or more MAC CEs indicatingone or more timing advance values for one or more Timing Advance Groups(TAGs).

FIG. 3 is a block diagram of base stations (base station 1, 120A, andbase station 2, 120B) and a wireless device 110. A wireless device maybe called an UE. A base station may be called a NB, eNB, gNB, and/orng-eNB. In an example, a wireless device and/or a base station may actas a relay node. The base station 1, 120A, may comprise at least onecommunication interface 320A (e.g. a wireless modem, an antenna, a wiredmodem, and/or the like), at least one processor 321A, and at least oneset of program code instructions 323A stored in non-transitory memory322A and executable by the at least one processor 321A. The base station2, 120B, may comprise at least one communication interface 320B, atleast one processor 321B, and at least one set of program codeinstructions 323B stored in non-transitory memory 322B and executable bythe at least one processor 321B.

A base station may comprise many sectors for example: 1, 2, 3, 4, or 6sectors. A base station may comprise many cells, for example, rangingfrom 1 to 50 cells or more. A cell may be categorized, for example, as aprimary cell or secondary cell. At Radio Resource Control (RRC)connection establishment/re-establishment/handover, one serving cell mayprovide the NAS (non-access stratum) mobility information (e.g. TrackingArea Identifier (TAI)). At RRC connection re-establishment/handover, oneserving cell may provide the security input. This cell may be referredto as the Primary Cell (PCell). In the downlink, a carrier correspondingto the PCell may be a DL Primary Component Carrier (PCC), while in theuplink, a carrier may be an UL PCC. Depending on wireless devicecapabilities, Secondary Cells (SCells) may be configured to formtogether with a PCell a set of serving cells. In a downlink, a carriercorresponding to an SCell may be a downlink secondary component carrier(DL SCC), while in an uplink, a carrier may be an uplink secondarycomponent carrier (UL SCC). An SCell may or may not have an uplinkcarrier.

A cell, comprising a downlink carrier and optionally an uplink carrier,may be assigned a physical cell ID and a cell index. A carrier (downlinkor uplink) may belong to one cell. The cell ID or cell index may alsoidentify the downlink carrier or uplink carrier of the cell (dependingon the context it is used). In the disclosure, a cell ID may be equallyreferred to a carrier ID, and a cell index may be referred to a carrierindex. In an implementation, a physical cell ID or a cell index may beassigned to a cell. A cell ID may be determined using a synchronizationsignal transmitted on a downlink carrier. A cell index may be determinedusing RRC messages. For example, when the disclosure refers to a firstphysical cell ID for a first downlink carrier, the disclosure may meanthe first physical cell ID is for a cell comprising the first downlinkcarrier. The same concept may apply to, for example, carrier activation.When the disclosure indicates that a first carrier is activated, thespecification may equally mean that a cell comprising the first carrieris activated.

A base station may transmit to a wireless device one or more messages(e.g. RRC messages) comprising a plurality of configuration parametersfor one or more cells. One or more cells may comprise at least oneprimary cell and at least one secondary cell. In an example, an RRCmessage may be broadcasted or unicasted to the wireless device. In anexample, configuration parameters may comprise common parameters anddedicated parameters.

Services and/or functions of an RRC sublayer may comprise at least oneof: broadcast of system information related to AS and NAS; paginginitiated by 5GC and/or NG-RAN; establishment, maintenance, and/orrelease of an RRC connection between a wireless device and NG-RAN, whichmay comprise at least one of addition, modification and release ofcarrier aggregation; or addition, modification, and/or release of dualconnectivity in NR or between E-UTRA and NR. Services and/or functionsof an RRC sublayer may further comprise at least one of securityfunctions comprising key management; establishment, configuration,maintenance, and/or release of Signaling Radio Bearers (SRBs) and/orData Radio Bearers (DRBs); mobility functions which may comprise atleast one of a handover (e.g. intra NR mobility or inter-RAT mobility)and a context transfer; or a wireless device cell selection andreselection and control of cell selection and reselection. Servicesand/or functions of an RRC sublayer may further comprise at least one ofQoS management functions; a wireless device measurementconfiguration/reporting; detection of and/or recovery from radio linkfailure; or NAS message transfer to/from a core network entity (e.g.AMF, Mobility Management Entity (MME)) from/to the wireless device.

An RRC sublayer may support an RRC_Idle state, an RRC_Inactive stateand/or an RRC_Connected state for a wireless device. In an RRC_Idlestate, a wireless device may perform at least one of: Public Land MobileNetwork (PLMN) selection; receiving broadcasted system information; cellselection/re-selection; monitoring/receiving a paging for mobileterminated data initiated by 5GC; paging for mobile terminated data areamanaged by 5GC; or DRX for CN paging configured via NAS. In anRRC_Inactive state, a wireless device may perform at least one of:receiving broadcasted system information; cell selection/re-selection;monitoring/receiving a RAN/CN paging initiated by NG-RAN/5GC; RAN-basednotification area (RNA) managed by NG-RAN; or DRX for RAN/CN pagingconfigured by NG-RAN/NAS. In an RRC_Idle state of a wireless device, abase station (e.g. NG-RAN) may keep a 5GC-NG-RAN connection (bothC/U-planes) for the wireless device; and/or store a UE AS context forthe wireless device. In an RRC_Connected state of a wireless device, abase station (e.g. NG-RAN) may perform at least one of: establishment of5GC-NG-RAN connection (both C/U-planes) for the wireless device; storinga UE AS context for the wireless device; transmit/receive of unicastdata to/from the wireless device; or network-controlled mobility basedon measurement results received from the wireless device. In anRRC_Connected state of a wireless device, an NG-RAN may know a cell thatthe wireless device belongs to.

System information (SI) may be divided into minimum SI and other SI. Theminimum SI may be periodically broadcast. The minimum SI may comprisebasic information required for initial access and information foracquiring any other SI broadcast periodically or provisioned on-demand,i.e. scheduling information. The other SI may either be broadcast, or beprovisioned in a dedicated manner, either triggered by a network or uponrequest from a wireless device. A minimum SI may be transmitted via twodifferent downlink channels using different messages (e.g.MasterInformationBlock and SystemInformationBlockType1). Another SI maybe transmitted via SystemInformationBlockType2. For a wireless device inan RRC_Connected state, dedicated RRC signaling may be employed for therequest and delivery of the other SI. For the wireless device in theRRC_Idle state and/or the RRC_Inactive state, the request may trigger arandom-access procedure.

A wireless device may report its radio access capability informationwhich may be static. A base station may request what capabilities for awireless device to report based on band information. When allowed by anetwork, a temporary capability restriction request may be sent by thewireless device to signal the limited availability of some capabilities(e.g. due to hardware sharing, interference or overheating) to the basestation. The base station may confirm or reject the request. Thetemporary capability restriction may be transparent to 5GC (e.g., staticcapabilities may be stored in 5GC).

When CA is configured, a wireless device may have an RRC connection witha network. At RRC connection establishment/re-establishment/handoverprocedure, one serving cell may provide NAS mobility information, and atRRC connection re-establishment/handover, one serving cell may provide asecurity input. This cell may be referred to as the PCell. Depending onthe capabilities of the wireless device, SCells may be configured toform together with the PCell a set of serving cells. The configured setof serving cells for the wireless device may comprise one PCell and oneor more SCells.

The reconfiguration, addition and removal of SCells may be performed byRRC. At intra-NR handover, RRC may also add, remove, or reconfigureSCells for usage with the target PCell. When adding a new SCell,dedicated RRC signaling may be employed to send all required systeminformation of the SCell i.e. while in connected mode, wireless devicesmay not need to acquire broadcasted system information directly from theSCells.

The purpose of an RRC connection reconfiguration procedure may be tomodify an RRC connection, (e.g. to establish, modify and/or release RBs,to perform handover, to setup, modify, and/or release measurements, toadd, modify, and/or release SCells and cell groups). As part of the RRCconnection reconfiguration procedure, NAS dedicated information may betransferred from the network to the wireless device. TheRRCConnectionReconfiguration message may be a command to modify an RRCconnection. It may convey information for measurement configuration,mobility control, radio resource configuration (e.g. RBs, MAC mainconfiguration and physical channel configuration) comprising anyassociated dedicated NAS information and security configuration. If thereceived RRC Connection Reconfiguration message includes thesCellToReleaseList, the wireless device may perform an SCell release. Ifthe received RRC Connection Reconfiguration message includes thesCellToAddModList, the wireless device may perform SCell additions ormodification.

An RRC connection establishment (or reestablishment, resume) proceduremay be to establish (or reestablish, resume) an RRC connection. an RRCconnection establishment procedure may comprise SRB1 establishment. TheRRC connection establishment procedure may be used to transfer theinitial NAS dedicated information/message from a wireless device toE-UTRAN. The RRCConnectionReestablishment message may be used tore-establish SRB1.

A measurement report procedure may be to transfer measurement resultsfrom a wireless device to NG-RAN. The wireless device may initiate ameasurement report procedure after successful security activation. Ameasurement report message may be employed to transmit measurementresults.

The wireless device 110 may comprise at least one communicationinterface 310 (e.g. a wireless modem, an antenna, and/or the like), atleast one processor 314, and at least one set of program codeinstructions 316 stored in non-transitory memory 315 and executable bythe at least one processor 314. The wireless device 110 may furthercomprise at least one of at least one speaker/microphone 311, at leastone keypad 312, at least one display/touchpad 313, at least one powersource 317, at least one global positioning system (GPS) chipset 318,and other peripherals 319.

The processor 314 of the wireless device 110, the processor 321A of thebase station 1 120A, and/or the processor 321B of the base station 2120B may comprise at least one of a general-purpose processor, a digitalsignal processor (DSP), a controller, a microcontroller, an applicationspecific integrated circuit (ASIC), a field programmable gate array(FPGA) and/or other programmable logic device, discrete gate and/ortransistor logic, discrete hardware components, and the like. Theprocessor 314 of the wireless device 110, the processor 321A in basestation 1 120A, and/or the processor 321B in base station 2 120B mayperform at least one of signal coding/processing, data processing, powercontrol, input/output processing, and/or any other functionality thatmay enable the wireless device 110, the base station 1 120A and/or thebase station 2 120B to operate in a wireless environment.

The processor 314 of the wireless device 110 may be connected to thespeaker/microphone 311, the keypad 312, and/or the display/touchpad 313.The processor 314 may receive user input data from and/or provide useroutput data to the speaker/microphone 311, the keypad 312, and/or thedisplay/touchpad 313. The processor 314 in the wireless device 110 mayreceive power from the power source 317 and/or may be configured todistribute the power to the other components in the wireless device 110.The power source 317 may comprise at least one of one or more dry cellbatteries, solar cells, fuel cells, and the like. The processor 314 maybe connected to the GPS chipset 318. The GPS chipset 318 may beconfigured to provide geographic location information of the wirelessdevice 110.

The processor 314 of the wireless device 110 may further be connected toother peripherals 319, which may comprise one or more software and/orhardware modules that provide additional features and/orfunctionalities. For example, the peripherals 319 may comprise at leastone of an accelerometer, a satellite transceiver, a digital camera, auniversal serial bus (USB) port, a hands-free headset, a frequencymodulated (FM) radio unit, a media player, an Internet browser, and thelike.

The communication interface 320A of the base station 1, 120A, and/or thecommunication interface 320B of the base station 2, 120B, may beconfigured to communicate with the communication interface 310 of thewireless device 110 via a wireless link 330A and/or a wireless link 330Brespectively. In an example, the communication interface 320A of thebase station 1, 120A, may communicate with the communication interface320B of the base station 2 and other RAN and core network nodes.

The wireless link 330A and/or the wireless link 330B may comprise atleast one of a bi-directional link and/or a directional link. Thecommunication interface 310 of the wireless device 110 may be configuredto communicate with the communication interface 320A of the base station1 120A and/or with the communication interface 320B of the base station2 120B. The base station 1 120A and the wireless device 110 and/or thebase station 2 120B and the wireless device 110 may be configured tosend and receive transport blocks via the wireless link 330A and/or viathe wireless link 330B, respectively. The wireless link 330A and/or thewireless link 330B may employ at least one frequency carrier. Accordingto some of various aspects of embodiments, transceiver(s) may beemployed. A transceiver may be a device that comprises both atransmitter and a receiver. Transceivers may be employed in devices suchas wireless devices, base stations, relay nodes, and/or the like.Example embodiments for radio technology implemented in thecommunication interface 310, 320A, 320B and the wireless link 330A, 330Bare illustrated in FIG. 4A, FIG. 4B, FIG. 4C, FIG. 4D, FIG. 6, FIG. 7A,FIG. 7B, FIG. 8, and associated text.

In an example, other nodes in a wireless network (e.g. AMF, UPF, SMF,etc.) may comprise one or more communication interfaces, one or moreprocessors, and memory storing instructions.

A node (e.g. wireless device, base station, AMF, SMF, UPF, servers,switches, antennas, and/or the like) may comprise one or moreprocessors, and memory storing instructions that when executed by theone or more processors causes the node to perform certain processesand/or functions. Example embodiments may enable operation ofsingle-carrier and/or multi-carrier communications. Other exampleembodiments may comprise a non-transitory tangible computer readablemedia comprising instructions executable by one or more processors tocause operation of single-carrier and/or multi-carrier communications.Yet other example embodiments may comprise an article of manufacturethat comprises a non-transitory tangible computer readablemachine-accessible medium having instructions encoded thereon forenabling programmable hardware to cause a node to enable operation ofsingle-carrier and/or multi-carrier communications. The node may includeprocessors, memory, interfaces, and/or the like.

An interface may comprise at least one of a hardware interface, afirmware interface, a software interface, and/or a combination thereof.The hardware interface may comprise connectors, wires, electronicdevices such as drivers, amplifiers, and/or the like. The softwareinterface may comprise code stored in a memory device to implementprotocol(s), protocol layers, communication drivers, device drivers,combinations thereof, and/or the like. The firmware interface maycomprise a combination of embedded hardware and code stored in and/or incommunication with a memory device to implement connections, electronicdevice operations, protocol(s), protocol layers, communication drivers,device drivers, hardware operations, combinations thereof, and/or thelike.

FIG. 4A, FIG. 4B, FIG. 4C and FIG. 4D are example diagrams for uplinkand downlink signal transmission as per an aspect of an embodiment ofthe present disclosure. FIG. 4A shows an example uplink transmitter forat least one physical channel. A baseband signal representing a physicaluplink shared channel may perform one or more functions. The one or morefunctions may comprise at least one of: scrambling; modulation ofscrambled bits to generate complex-valued symbols; mapping of thecomplex-valued modulation symbols onto one or several transmissionlayers; transform precoding to generate complex-valued symbols;precoding of the complex-valued symbols; mapping of precodedcomplex-valued symbols to resource elements; generation ofcomplex-valued time-domain Single Carrier-Frequency Division MultipleAccess (SC-FDMA) or CP-OFDM signal for an antenna port; and/or the like.In an example, when transform precoding is enabled, a SC-FDMA signal foruplink transmission may be generated. In an example, when transformprecoding is not enabled, an CP-OFDM signal for uplink transmission maybe generated by FIG. 4A. These functions are illustrated as examples andit is anticipated that other mechanisms may be implemented in variousembodiments.

An example structure for modulation and up-conversion to the carrierfrequency of the complex-valued SC-FDMA or CP-OFDM baseband signal foran antenna port and/or the complex-valued Physical Random Access CHannel(PRACH) baseband signal is shown in FIG. 4B. Filtering may be employedprior to transmission.

An example structure for downlink transmissions is shown in FIG. 4C. Thebaseband signal representing a downlink physical channel may perform oneor more functions. The one or more functions may comprise: scrambling ofcoded bits in a codeword to be transmitted on a physical channel;modulation of scrambled bits to generate complex-valued modulationsymbols; mapping of the complex-valued modulation symbols onto one orseveral transmission layers; precoding of the complex-valued modulationsymbols on a layer for transmission on the antenna ports; mapping ofcomplex-valued modulation symbols for an antenna port to resourceelements; generation of complex-valued time-domain OFDM signal for anantenna port; and/or the like. These functions are illustrated asexamples and it is anticipated that other mechanisms may be implementedin various embodiments.

In an example, a gNB may transmit a first symbol and a second symbol onan antenna port, to a wireless device. The wireless device may infer thechannel (e.g., fading gain, multipath delay, etc.) for conveying thesecond symbol on the antenna port, from the channel for conveying thefirst symbol on the antenna port. In an example, a first antenna portand a second antenna port may be quasi co-located if one or morelarge-scale properties of the channel over which a first symbol on thefirst antenna port is conveyed may be inferred from the channel overwhich a second symbol on a second antenna port is conveyed. The one ormore large-scale properties may comprise at least one of: delay spread;doppler spread; doppler shift; average gain; average delay; and/orspatial Receiving (Rx) parameters.

An example modulation and up-conversion to the carrier frequency of thecomplex-valued OFDM baseband signal for an antenna port is shown in FIG.4D. Filtering may be employed prior to transmission.

FIG. 5A is a diagram of an example uplink channel mapping and exampleuplink physical signals. FIG. 5B is a diagram of an example downlinkchannel mapping and a downlink physical signals. In an example, aphysical layer may provide one or more information transfer services toa MAC and/or one or more higher layers. For example, the physical layermay provide the one or more information transfer services to the MAC viaone or more transport channels. An information transfer service mayindicate how and with what characteristics data are transferred over theradio interface.

In an example embodiment, a radio network may comprise one or moredownlink and/or uplink transport channels. For example, a diagram inFIG. 5A shows example uplink transport channels comprising Uplink-SharedCHannel (UL-SCH) 501 and Random Access CHannel (RACH) 502. A diagram inFIG. 5B shows example downlink transport channels comprisingDownlink-Shared CHannel (DL-SCH) 511, Paging CHannel (PCH) 512, andBroadcast CHannel (BCH) 513. A transport channel may be mapped to one ormore corresponding physical channels. For example, UL-SCH 501 may bemapped to Physical Uplink Shared CHannel (PUSCH) 503. RACH 502 may bemapped to PRACH 505. DL-SCH 511 and PCH 512 may be mapped to PhysicalDownlink Shared CHannel (PDSCH) 514. BCH 513 may be mapped to PhysicalBroadcast CHannel (PBCH) 516.

There may be one or more physical channels without a correspondingtransport channel. The one or more physical channels may be employed forUplink Control Information (UCI) 509 and/or Downlink Control Information(DCI) 517. For example, Physical Uplink Control CHannel (PUCCH) 504 maycarry UCI 509 from a UE to a base station. For example, PhysicalDownlink Control CHannel (PDCCH) 515 may carry DCI 517 from a basestation to a UE. NR may support UCI 509 multiplexing in PUSCH 503 whenUCI 509 and PUSCH 503 transmissions may coincide in a slot at least inpart. The UCI 509 may comprise at least one of CSI, Acknowledgement(ACK)/Negative Acknowledgement (NACK), and/or scheduling request. TheDCI 517 on PDCCH 515 may indicate at least one of following: one or moredownlink assignments and/or one or more uplink scheduling grants

In uplink, a UE may transmit one or more Reference Signals (RSs) to abase station. For example, the one or more RSs may be at least one ofDemodulation-RS (DM-RS) 506, Phase Tracking-RS (PT-RS) 507, and/orSounding RS (SRS) 508. In downlink, a base station may transmit (e.g.,unicast, multicast, and/or broadcast) one or more RSs to a UE. Forexample, the one or more RSs may be at least one of PrimarySynchronization Signal (PSS)/Secondary Synchronization Signal (SSS) 521,CSI-RS 522, DM-RS 523, and/or PT-RS 524.

In an example, a UE may transmit one or more uplink DM-RSs 506 to a basestation for channel estimation, for example, for coherent demodulationof one or more uplink physical channels (e.g., PUSCH 503 and/or PUCCH504). For example, a UE may transmit a base station at least one uplinkDM-RS 506 with PUSCH 503 and/or PUCCH 504, wherein the at least oneuplink DM-RS 506 may be spanning a same frequency range as acorresponding physical channel. In an example, a base station mayconfigure a UE with one or more uplink DM-RS configurations. At leastone DM-RS configuration may support a front-loaded DM-RS pattern. Afront-loaded DM-RS may be mapped over one or more OFDM symbols (e.g., 1or 2 adjacent OFDM symbols). One or more additional uplink DM-RS may beconfigured to transmit at one or more symbols of a PUSCH and/or PUCCH. Abase station may semi-statistically configure a UE with a maximum numberof front-loaded DM-RS symbols for PUSCH and/or PUCCH. For example, a UEmay schedule a single-symbol DM-RS and/or double symbol DM-RS based on amaximum number of front-loaded DM-RS symbols, wherein a base station mayconfigure the UE with one or more additional uplink DM-RS for PUSCHand/or PUCCH. A new radio network may support, e.g., at least forCP-OFDM, a common DM-RS structure for DL and UL, wherein a DM-RSlocation, DM-RS pattern, and/or scrambling sequence may be same ordifferent.

In an example, whether uplink PT-RS 507 is present or not may depend ona RRC configuration. For example, a presence of uplink PT-RS may beUE-specifically configured. For example, a presence and/or a pattern ofuplink PT-RS 507 in a scheduled resource may be UE-specificallyconfigured by a combination of RRC signaling and/or association with oneor more parameters employed for other purposes (e.g., Modulation andCoding Scheme (MCS)) which may be indicated by DCI. When configured, adynamic presence of uplink PT-RS 507 may be associated with one or moreDCI parameters comprising at least MCS. A radio network may supportplurality of uplink PT-RS densities defined in time/frequency domain.When present, a frequency domain density may be associated with at leastone configuration of a scheduled bandwidth. A UE may assume a sameprecoding for a DMRS port and a PT-RS port. A number of PT-RS ports maybe fewer than a number of DM-RS ports in a scheduled resource. Forexample, uplink PT-RS 507 may be confined in the scheduledtime/frequency duration for a UE.

In an example, a UE may transmit SRS 508 to a base station for channelstate estimation to support uplink channel dependent scheduling and/orlink adaptation. For example, SRS 508 transmitted by a UE may allow fora base station to estimate an uplink channel state at one or moredifferent frequencies. A base station scheduler may employ an uplinkchannel state to assign one or more resource blocks of good quality foran uplink PUSCH transmission from a UE. A base station maysemi-statistically configure a UE with one or more SRS resource sets.For an SRS resource set, a base station may configure a UE with one ormore SRS resources. An SRS resource set applicability may be configuredby a higher layer (e.g., RRC) parameter. For example, when a higherlayer parameter indicates beam management, a SRS resource in each of oneor more SRS resource sets may be transmitted at a time instant. A UE maytransmit one or more SRS resources in different SRS resource setssimultaneously. A new radio network may support aperiodic, periodicand/or semi-persistent SRS transmissions. A UE may transmit SRSresources based on one or more trigger types, wherein the one or moretrigger types may comprise higher layer signaling (e.g., RRC) and/or oneor more DCI formats (e.g., at least one DCI format may be employed for aUE to select at least one of one or more configured SRS resource sets.An SRS trigger type 0 may refer to an SRS triggered based on a higherlayer signaling. An SRS trigger type 1 may refer to an SRS triggeredbased on one or more DCI formats. In an example, when PUSCH 503 and SRS508 are transmitted in a same slot, a UE may be configured to transmitSRS 508 after a transmission of PUSCH 503 and corresponding uplink DM-RS506.

In an example, a base station may semi-statistically configure a UE withone or more SRS configuration parameters indicating at least one offollowing: a SRS resource configuration identifier, a number of SRSports, time domain behavior of SRS resource configuration (e.g., anindication of periodic, semi-persistent, or aperiodic SRS), slot(mini-slot, and/or subframe) level periodicity and/or offset for aperiodic and/or aperiodic SRS resource, a number of OFDM symbols in aSRS resource, starting OFDM symbol of a SRS resource, a SRS bandwidth, afrequency hopping bandwidth, a cyclic shift, and/or a SRS sequence ID.

In an example, in a time domain, an SS/PBCH block may comprise one ormore OFDM symbols (e.g., 4 OFDM symbols numbered in increasing orderfrom 0 to 3) within the SS/PBCH block. An SS/PBCH block may comprisePSS/SSS 521 and PBCH 516. In an example, in the frequency domain, anSS/PBCH block may comprise one or more contiguous subcarriers (e.g., 240contiguous subcarriers with the subcarriers numbered in increasing orderfrom 0 to 239) within the SS/PBCH block. For example, a PSS/SSS 521 mayoccupy 1 OFDM symbol and 127 subcarriers. For example, PBCH 516 may spanacross 3 OFDM symbols and 240 subcarriers. A UE may assume that one ormore SS/PBCH blocks transmitted with a same block index may be quasico-located, e.g., with respect to Doppler spread, Doppler shift, averagegain, average delay, and spatial Rx parameters. A UE may not assumequasi co-location for other SS/PBCH block transmissions. A periodicityof an SS/PBCH block may be configured by a radio network (e.g., by anRRC signaling) and one or more time locations where the SS/PBCH blockmay be sent may be determined by sub-carrier spacing. In an example, aUE may assume a band-specific sub-carrier spacing for an SS/PBCH blockunless a radio network has configured a UE to assume a differentsub-carrier spacing.

In an example, downlink CSI-RS 522 may be employed for a UE to acquirechannel state information. A radio network may support periodic,aperiodic, and/or semi-persistent transmission of downlink CSI-RS 522.For example, a base station may semi-statistically configure and/orreconfigure a UE with periodic transmission of downlink CSI-RS 522. Aconfigured CSI-RS resources may be activated ad/or deactivated. Forsemi-persistent transmission, an activation and/or deactivation ofCSI-RS resource may be triggered dynamically. In an example, CSI-RSconfiguration may comprise one or more parameters indicating at least anumber of antenna ports. For example, a base station may configure a UEwith 32 ports. A base station may semi-statistically configure a UE withone or more CSI-RS resource sets. One or more CSI-RS resources may beallocated from one or more CSI-RS resource sets to one or more UEs. Forexample, a base station may semi-statistically configure one or moreparameters indicating CSI RS resource mapping, for example, time-domainlocation of one or more CSI-RS resources, a bandwidth of a CSI-RSresource, and/or a periodicity. In an example, a UE may be configured toemploy a same OFDM symbols for downlink CSI-RS 522 and control resourceset (coreset) when the downlink CSI-RS 522 and coreset are spatiallyquasi co-located and resource elements associated with the downlinkCSI-RS 522 are the outside of PRB s configured for coreset. In anexample, a UE may be configured to employ a same OFDM symbols fordownlink CSI-RS 522 and SSB/PBCH when the downlink CSI-RS 522 andSSB/PBCH are spatially quasi co-located and resource elements associatedwith the downlink CSI-RS 522 are the outside of PRBs configured forSSB/PBCH.

In an example, a UE may transmit one or more downlink DM-RSs 523 to abase station for channel estimation, for example, for coherentdemodulation of one or more downlink physical channels (e.g., PDSCH514). For example, a radio network may support one or more variableand/or configurable DM-RS patterns for data demodulation. At least onedownlink DM-RS configuration may support a front-loaded DM-RS pattern. Afront-loaded DM-RS may be mapped over one or more OFDM symbols (e.g., 1or 2 adjacent OFDM symbols). A base station may semi-statisticallyconfigure a UE with a maximum number of front-loaded DM-RS symbols forPDSCH 514. For example, a DM-RS configuration may support one or moreDM-RS ports. For example, for single user-MIMO, a DM-RS configurationmay support at least 8 orthogonal downlink DM-RS ports. For example, formultiuser-MIMO, a DM-RS configuration may support 12 orthogonal downlinkDM-RS ports. A radio network may support, e.g., at least for CP-OFDM, acommon DM-RS structure for DL and UL, wherein a DM-RS location, DM-RSpattern, and/or scrambling sequence may be same or different.

In an example, whether downlink PT-RS 524 is present or not may dependon a RRC configuration. For example, a presence of downlink PT-RS 524may be UE-specifically configured. For example, a presence and/or apattern of downlink PT-RS 524 in a scheduled resource may beUE-specifically configured by a combination of RRC signaling and/orassociation with one or more parameters employed for other purposes(e.g., MCS) which may be indicated by DCI. When configured, a dynamicpresence of downlink PT-RS 524 may be associated with one or more DCIparameters comprising at least MCS. A radio network may supportplurality of PT-RS densities defined in time/frequency domain. Whenpresent, a frequency domain density may be associated with at least oneconfiguration of a scheduled bandwidth. A UE may assume a same precodingfor a DMRS port and a PT-RS port. A number of PT-RS ports may be fewerthan a number of DM-RS ports in a scheduled resource. For example,downlink PT-RS 524 may be confined in the scheduled time/frequencyduration for a UE.

FIG. 6 is a diagram depicting an example frame structure for a carrieras per an aspect of an embodiment of the present disclosure. Amulticarrier OFDM communication system may include one or more carriers,for example, ranging from 1 to 32 carriers, in case of carrieraggregation, or ranging from 1 to 64 carriers, in case of dualconnectivity. Different radio frame structures may be supported (e.g.,for FDD and for TDD duplex mechanisms). FIG. 6 shows an example framestructure. Downlink and uplink transmissions may be organized into radioframes 601. In this example, radio frame duration is 10 ms. In thisexample, a 10 ms radio frame 601 may be divided into ten equally sizedsubframes 602 with 1 ms duration. Subframe(s) may comprise one or moreslots (e.g. slots 603 and 605) depending on subcarrier spacing and/or CPlength. For example, a subframe with 15 kHz, 30 kHz, 60 kHz, 120 kHz,240 kHz and 480 kHz subcarrier spacing may comprise one, two, four,eight, sixteen and thirty-two slots, respectively. In FIG. 6, a subframemay be divided into two equally sized slots 603 with 0.5 ms duration.For example, 10 subframes may be available for downlink transmission and10 subframes may be available for uplink transmissions in a 10 msinterval. Uplink and downlink transmissions may be separated in thefrequency domain. Slot(s) may include a plurality of OFDM symbols 604.The number of OFDM symbols 604 in a slot 605 may depend on the cyclicprefix length. For example, a slot may be 14 OFDM symbols for the samesubcarrier spacing of up to 480 kHz with normal CP. A slot may be 12OFDM symbols for the same subcarrier spacing of 60 kHz with extended CP.A slot may contain downlink, uplink, or a downlink part and an uplinkpart and/or alike.

FIG. 7A is a diagram depicting example sets of OFDM subcarriers as peran aspect of an embodiment of the present disclosure. In the example, agNB may communicate with a wireless device with a carrier with anexample channel bandwidth 700. Arrow(s) in the diagram may depict asubcarrier in a multicarrier OFDM system. The OFDM system may usetechnology such as OFDM technology, SC-FDMA technology, and/or the like.In an example, an arrow 701 shows a subcarrier transmitting informationsymbols. In an example, a subcarrier spacing 702, between two contiguoussubcarriers in a carrier, may be any one of 15 KHz, 30 KHz, 60 KHz, 120KHz, 240 KHz etc. In an example, different subcarrier spacing maycorrespond to different transmission numerologies. In an example, atransmission numerology may comprise at least: a numerology index; avalue of subcarrier spacing; a type of cyclic prefix (CP). In anexample, a gNB may transmit to/receive from a UE on a number ofsubcarriers 703 in a carrier. In an example, a bandwidth occupied by anumber of subcarriers 703 (transmission bandwidth) may be smaller thanthe channel bandwidth 700 of a carrier, due to guard band 704 and 705.In an example, a guard band 704 and 705 may be used to reduceinterference to and from one or more neighbor carriers. A number ofsubcarriers (transmission bandwidth) in a carrier may depend on thechannel bandwidth of the carrier and the subcarrier spacing. Forexample, a transmission bandwidth, for a carrier with 20 MHz channelbandwidth and 15 KHz subcarrier spacing, may be in number of 1024subcarriers.

In an example, a gNB and a wireless device may communicate with multipleCCs when configured with CA. In an example, different component carriersmay have different bandwidth and/or subcarrier spacing, if CA issupported. In an example, a gNB may transmit a first type of service toa UE on a first component carrier. The gNB may transmit a second type ofservice to the UE on a second component carrier. Different type ofservices may have different service requirement (e.g., data rate,latency, reliability), which may be suitable for transmission viadifferent component carrier having different subcarrier spacing and/orbandwidth. FIG. 7B shows an example embodiment. A first componentcarrier may comprise a first number of subcarriers 706 with a firstsubcarrier spacing 709. A second component carrier may comprise a secondnumber of subcarriers 707 with a second subcarrier spacing 710. A thirdcomponent carrier may comprise a third number of subcarriers 708 with athird subcarrier spacing 711. Carriers in a multicarrier OFDMcommunication system may be contiguous carriers, non-contiguouscarriers, or a combination of both contiguous and non-contiguouscarriers.

FIG. 8 is a diagram depicting OFDM radio resources as per an aspect ofan embodiment of the present disclosure. In an example, a carrier mayhave a transmission bandwidth 801. In an example, a resource grid may bein a structure of frequency domain 802 and time domain 803. In anexample, a resource grid may comprise a first number of OFDM symbols ina subframe and a second number of resource blocks, starting from acommon resource block indicated by higher-layer signaling (e.g. RRCsignaling), for a transmission numerology and a carrier. In an example,in a resource grid, a resource unit identified by a subcarrier index anda symbol index may be a resource element 805. In an example, a subframemay comprise a first number of OFDM symbols 807 depending on anumerology associated with a carrier. For example, when a subcarrierspacing of a numerology of a carrier is 15 KHz, a subframe may have 14OFDM symbols for a carrier. When a subcarrier spacing of a numerology is30 KHz, a subframe may have 28 OFDM symbols. When a subcarrier spacingof a numerology is 60 Khz, a subframe may have 56 OFDM symbols, etc. Inan example, a second number of resource blocks comprised in a resourcegrid of a carrier may depend on a bandwidth and a numerology of thecarrier.

As shown in FIG. 8, a resource block 806 may comprise 12 subcarriers. Inan example, multiple resource blocks may be grouped into a ResourceBlock Group (RBG) 804. In an example, a size of a RBG may depend on atleast one of: a RRC message indicating a RBG size configuration; a sizeof a carrier bandwidth; or a size of a bandwidth part of a carrier. Inan example, a carrier may comprise multiple bandwidth parts. A firstbandwidth part of a carrier may have different frequency location and/orbandwidth from a second bandwidth part of the carrier.

In an example, a gNB may transmit a downlink control informationcomprising a downlink or uplink resource block assignment to a wirelessdevice. A base station may transmit to or receive from, a wirelessdevice, data packets (e.g. transport blocks) scheduled and transmittedvia one or more resource blocks and one or more slots according toparameters in a downlink control information and/or RRC message(s). Inan example, a starting symbol relative to a first slot of the one ormore slots may be indicated to the wireless device. In an example, a gNBmay transmit to or receive from, a wireless device, data packetsscheduled on one or more RBGs and one or more slots.

In an example, a gNB may transmit a downlink control informationcomprising a downlink assignment to a wireless device via one or morePDCCHs. The downlink assignment may comprise parameters indicating atleast modulation and coding format; resource allocation; and/or HARQinformation related to DL-SCH. In an example, a resource allocation maycomprise parameters of resource block allocation; and/or slotallocation. In an example, a gNB may dynamically allocate resources to awireless device via a Cell-Radio Network Temporary Identifier (C-RNTI)on one or more PDCCHs. The wireless device may monitor the one or morePDCCHs in order to find possible allocation when its downlink receptionis enabled. The wireless device may receive one or more downlink datapackage on one or more PDSCH scheduled by the one or more PDCCHs, whensuccessfully detecting the one or more PDCCHs.

In an example, a gNB may allocate Configured Scheduling (CS) resourcesfor down link transmission to a wireless device. The gNB may transmitone or more RRC messages indicating a periodicity of the CS grant. ThegNB may transmit a DCI via a PDCCH addressed to a ConfiguredScheduling-RNTI (CS-RNTI) activating the CS resources. The DCI maycomprise parameters indicating that the downlink grant is a CS grant.The CS grant may be implicitly reused according to the periodicitydefined by the one or more RRC messages, until deactivated.

In an example, a gNB may transmit a downlink control informationcomprising an uplink grant to a wireless device via one or more PDCCHs.The uplink grant may comprise parameters indicating at least modulationand coding format; resource allocation; and/or HARQ information relatedto UL-SCH. In an example, a resource allocation may comprise parametersof resource block allocation; and/or slot allocation. In an example, agNB may dynamically allocate resources to a wireless device via a C-RNTIon one or more PDCCHs. The wireless device may monitor the one or morePDCCHs in order to find possible resource allocation. The wirelessdevice may transmit one or more uplink data package via one or morePUSCH scheduled by the one or more PDCCHs, when successfully detectingthe one or more PDCCHs.

In an example, a gNB may allocate CS resources for uplink datatransmission to a wireless device. The gNB may transmit one or more RRCmessages indicating a periodicity of the CS grant. The gNB may transmita DCI via a PDCCH addressed to a CS-RNTI activating the CS resources.The DCI may comprise parameters indicating that the uplink grant is a CSgrant. The CS grant may be implicitly reused according to theperiodicity defined by the one or more RRC message, until deactivated.

In an example, a base station may transmit DCI/control signaling viaPDCCH. The DCI may take a format in a plurality of formats. A DCI maycomprise downlink and/or uplink scheduling information (e.g., resourceallocation information, HARQ related parameters, MCS), request for CSI(e.g., aperiodic CQI reports), request for SRS, uplink power controlcommands for one or more cells, one or more timing information (e.g., TBtransmission/reception timing, HARQ feedback timing, etc.), etc. In anexample, a DCI may indicate an uplink grant comprising transmissionparameters for one or more transport blocks. In an example, a DCI mayindicate downlink assignment indicating parameters for receiving one ormore transport blocks. In an example, a DCI may be used by base stationto initiate a contention-free random access at the wireless device. Inan example, the base station may transmit a DCI comprising slot formatindicator (SFI) notifying a slot format. In an example, the base stationmay transmit a DCI comprising pre-emption indication notifying thePRB(s) and/or OFDM symbol(s) where a UE may assume no transmission isintended for the UE. In an example, the base station may transmit a DCIfor group power control of PUCCH or PUSCH or SRS. In an example, a DCImay correspond to an RNTI. In an example, the wireless device may obtainan RNTI in response to completing the initial access (e.g., C-RNTI). Inan example, the base station may configure an RNTI for the wireless(e.g., CS-RNTI, TPC-CS-RNTI, TPC-PUCCH-RNTI, TPC-PUSCH-RNTI,TPC-SRS-RNTI). In an example, the wireless device may compute an RNTI(e.g., the wireless device may compute RA-RNTI based on resources usedfor transmission of a preamble). In an example, an RNTI may have apre-configured value (e.g., P-RNTI or SI-RNTI). In an example, awireless device may monitor a group common search space which may beused by base station for transmitting DCIs that are intended for a groupof UEs. In an example, a group common DCI may correspond to an RNTIwhich is commonly configured for a group of UEs. In an example, awireless device may monitor a UE-specific search space. In an example, aUE specific DCI may correspond to an RNTI configured for the wirelessdevice.

A NR system may support a single beam operation and/or a multi-beamoperation. In a multi-beam operation, a base station may perform adownlink beam sweeping to provide coverage for common control channelsand/or downlink SS blocks, which may comprise at least a PSS, a SSS,and/or PBCH. A wireless device may measure quality of a beam pair linkusing one or more RS s. One or more SS blocks, or one or more CSI-RSresources, associated with a CSI-RS resource index (CRI), or one or moreDM-RSs of PBCH, may be used as RS for measuring quality of a beam pairlink. Quality of a beam pair link may be defined as a reference signalreceived power (RSRP) value, or a reference signal received quality(RSRQ) value, and/or a CSI value measured on RS resources. The basestation may indicate whether an RS resource, used for measuring a beampair link quality, is quasi-co-located (QCLed) with DM-RSs of a controlchannel. A RS resource and DM-RSs of a control channel may be calledQCLed when a channel characteristics from a transmission on an RS to awireless device, and that from a transmission on a control channel to awireless device, are similar or same under a configured criterion. In amulti-beam operation, a wireless device may perform an uplink beamsweeping to access a cell.

In an example, a wireless device may be configured to monitor PDCCH onone or more beam pair links simultaneously depending on a capability ofa wireless device. This may increase robustness against beam pair linkblocking. A base station may transmit one or more messages to configurea wireless device to monitor PDCCH on one or more beam pair links indifferent PDCCH OFDM symbols. For example, a base station may transmithigher layer signaling (e.g. RRC signaling) or MAC CE comprisingparameters related to the Rx beam setting of a wireless device formonitoring PDCCH on one or more beam pair links. A base station maytransmit indication of spatial QCL assumption between an DL RS antennaport(s) (for example, cell-specific CSI-RS, or wireless device-specificCSI-RS, or SS block, or PBCH with or without DM-RSs of PBCH), and DL RSantenna port(s) for demodulation of DL control channel. Signaling forbeam indication for a PDCCH may be MAC CE signaling, or RRC signaling,or DCI signaling, or specification-transparent and/or implicit method,and combination of these signaling methods.

For reception of unicast DL data channel, a base station may indicatespatial QCL parameters between DL RS antenna port(s) and DM-RS antennaport(s) of DL data channel. The base station may transmit DCI (e.g.downlink grants) comprising information indicating the RS antennaport(s). The information may indicate RS antenna port(s) which may beQCL-ed with the DM-RS antenna port(s). Different set of DM-RS antennaport(s) for a DL data channel may be indicated as QCL with different setof the RS antenna port(s).

FIG. 9A is an example of beam sweeping in a DL channel. In anRRC_INACTIVE state or RRC_IDLE state, a wireless device may assume thatSS blocks form an SS burst 940, and an SS burst set 950. The SS burstset 950 may have a given periodicity. For example, in a multi-beamoperation, a base station 120 may transmit SS blocks in multiple beams,together forming a SS burst 940. One or more SS blocks may betransmitted on one beam. If multiple SS bursts 940 are transmitted withmultiple beams, SS bursts together may form SS burst set 950.

A wireless device may further use CSI-RS in the multi-beam operation forestimating a beam quality of a links between a wireless device and abase station. A beam may be associated with a CSI-RS. For example, awireless device may, based on a RSRP measurement on CSI-RS, report abeam index, as indicated in a CRI for downlink beam selection, andassociated with a RSRP value of a beam. A CSI-RS may be transmitted on aCSI-RS resource including at least one of one or more antenna ports, oneor more time or frequency radio resources. A CSI-RS resource may beconfigured in a cell-specific way by common RRC signaling, or in awireless device-specific way by dedicated RRC signaling, and/or L1/L2signaling. Multiple wireless devices covered by a cell may measure acell-specific CSI-RS resource. A dedicated subset of wireless devicescovered by a cell may measure a wireless device-specific CSI-RSresource.

A CSI-RS resource may be transmitted periodically, or using aperiodictransmission, or using a multi-shot or semi-persistent transmission. Forexample, in a periodic transmission in FIG. 9A, a base station 120 maytransmit configured CSI-RS resources 940 periodically using a configuredperiodicity in a time domain. In an aperiodic transmission, a configuredCSI-RS resource may be transmitted in a dedicated time slot. In amulti-shot or semi-persistent transmission, a configured CSI-RS resourcemay be transmitted within a configured period. Beams used for CSI-RStransmission may have different beam width than beams used for SS-blockstransmission.

FIG. 9B is an example of a beam management procedure in an example newradio network. A base station 120 and/or a wireless device 110 mayperform a downlink L1/L2 beam management procedure. One or more of thefollowing downlink L1/L2 beam management procedures may be performedwithin one or more wireless devices 110 and one or more base stations120. In an example, a P-1 procedure 910 may be used to enable thewireless device 110 to measure one or more Transmission (Tx) beamsassociated with the base station 120 to support a selection of a firstset of Tx beams associated with the base station 120 and a first set ofRx beam(s) associated with a wireless device 110. For beamforming at abase station 120, a base station 120 may sweep a set of different TXbeams. For beamforming at a wireless device 110, a wireless device 110may sweep a set of different Rx beams. In an example, a P-2 procedure920 may be used to enable a wireless device 110 to measure one or moreTx beams associated with a base station 120 to possibly change a firstset of Tx beams associated with a base station 120. A P-2 procedure 920may be performed on a possibly smaller set of beams for beam refinementthan in the P-1 procedure 910. A P-2 procedure 920 may be a special caseof a P-1 procedure 910. In an example, a P-3 procedure 930 may be usedto enable a wireless device 110 to measure at least one Tx beamassociated with a base station 120 to change a first set of Rx beamsassociated with a wireless device 110.

A wireless device 110 may transmit one or more beam management reportsto a base station 120. In one or more beam management reports, awireless device 110 may indicate some beam pair quality parameters,comprising at least, one or more beam identifications; RSRP; PrecodingMatrix Indicator (PMI)/Channel Quality Indicator (CQI)/Rank Indicator(RI) of a subset of configured beams. Based on one or more beammanagement reports, a base station 120 may transmit to a wireless device110 a signal indicating that one or more beam pair links are one or moreserving beams. A base station 120 may transmit PDCCH and PDSCH for awireless device 110 using one or more serving beams.

In an example embodiment, new radio network may support a BandwidthAdaptation (BA). In an example, receive and/or transmit bandwidthsconfigured by an UE employing a BA may not be large. For example, areceive and/or transmit bandwidths may not be as large as a bandwidth ofa cell. Receive and/or transmit bandwidths may be adjustable. Forexample, a UE may change receive and/or transmit bandwidths, e.g., toshrink during period of low activity to save power. For example, a UEmay change a location of receive and/or transmit bandwidths in afrequency domain, e.g. to increase scheduling flexibility. For example,a UE may change a subcarrier spacing, e.g. to allow different services.

In an example embodiment, a subset of a total cell bandwidth of a cellmay be referred to as a Bandwidth Part (BWP). A base station mayconfigure a UE with one or more BWPs to achieve a BA. For example, abase station may indicate, to a UE, which of the one or more(configured) BWPs is an active BWP.

FIG. 10 is an example diagram of 3 BWPs configured: BWP1 (1010 and 1050)with a width of 40 MHz and subcarrier spacing of 15 kHz; BWP2 (1020 and1040) with a width of 10 MHz and subcarrier spacing of 15 kHz; BWP3 1030with a width of 20 MHz and subcarrier spacing of 60 kHz.

In an example, a UE, configured for operation in one or more BWPs of acell, may be configured by one or more higher layers (e.g. RRC layer)for a cell a set of one or more BWPs (e.g., at most four BWPs) forreceptions by the UE (DL BWP set) in a DL bandwidth by at least oneparameter DL-BWP and a set of one or more BWPs (e.g., at most four BWPs)for transmissions by a UE (UL BWP set) in an UL bandwidth by at leastone parameter UL-BWP for a cell.

To enable BA on the PCell, a base station may configure a UE with one ormore UL and DL BWP pairs. To enable BA on SCells (e.g., in case of CA),a base station may configure a UE at least with one or more DL BWPs(e.g., there may be none in an UL).

In an example, an initial active DL BWP may be defined by at least oneof a location and number of contiguous PRBs, a subcarrier spacing, or acyclic prefix, for a control resource set for at least one common searchspace. For operation on the PCell, one or more higher layer parametersmay indicate at least one initial UL BWP for a random access procedure.If a UE is configured with a secondary carrier on a primary cell, the UEmay be configured with an initial BWP for random access procedure on asecondary carrier.

In an example, for unpaired spectrum operation, a UE may expect that acenter frequency for a DL BWP may be same as a center frequency for a ULBWP.

For example, for a DL BWP or an UL BWP in a set of one or more DL BWPsor one or more UL BWPs, respectively, a base statin maysemi-statistically configure a UE for a cell with one or more parametersindicating at least one of following: a subcarrier spacing; a cyclicprefix; a number of contiguous PRBs; an index in the set of one or moreDL BWPs and/or one or more UL BWPs; a link between a DL BWP and an ULBWP from a set of configured DL BWPs and UL BWPs; a DCI detection to aPDSCH reception timing; a PDSCH reception to a HARQ-ACK transmissiontiming value; a DCI detection to a PUSCH transmission timing value; anoffset of a first PRB of a DL bandwidth or an UL bandwidth,respectively, relative to a first PRB of a bandwidth.

In an example, for a DL BWP in a set of one or more DL BWPs on a PCell,a base station may configure a UE with one or more control resource setsfor at least one type of common search space and/or one UE-specificsearch space. For example, a base station may not configure a UE withouta common search space on a PCell, or on a PSCell, in an active DL BWP.

For an UL BWP in a set of one or more UL BWPs, a base station mayconfigure a UE with one or more resource sets for one or more PUCCHtransmissions.

In an example, if a DCI comprises a BWP indicator field, a BWP indicatorfield value may indicate an active DL BWP, from a configured DL BWP set,for one or more DL receptions. If a DCI comprises a BWP indicator field,a BWP indicator field value may indicate an active UL BWP, from aconfigured UL BWP set, for one or more UL transmissions.

In an example, for a PCell, a base station may semi-statisticallyconfigure a UE with a default DL BWP among configured DL BWPs. If a UEis not provided a default DL BWP, a default BWP may be an initial activeDL BWP.

In an example, a base station may configure a UE with a timer value fora PCell. For example, a UE may start a timer, referred to as BWPinactivity timer, when a UE detects a DCI indicating an active DL BWP,other than a default DL BWP, for a paired spectrum operation or when aUE detects a DCI indicating an active DL BWP or UL BWP, other than adefault DL BWP or UL BWP, for an unpaired spectrum operation. The UE mayincrement the timer by an interval of a first value (e.g., the firstvalue may be 1 millisecond or 0.5 milliseconds) if the UE does notdetect a DCI during the interval for a paired spectrum operation or foran unpaired spectrum operation. In an example, the timer may expire whenthe timer is equal to the timer value. A UE may switch to the default DLBWP from an active DL BWP when the timer expires.

In an example, a base station may semi-statistically configure a UE withone or more BWPs. A UE may switch an active BWP from a first BWP to asecond BWP in response to receiving a DCI indicating the second BWP asan active BWP and/or in response to an expiry of BWP inactivity timer(for example, the second BWP may be a default BWP). For example, FIG. 10is an example diagram of 3 BWPs configured, BWP1 (1010 and 1050), BWP2(1020 and 1040), and BWP3 (1030). BWP2 (1020 and 1040) may be a defaultBWP. BWP1 (1010) may be an initial active BWP. In an example, a UE mayswitch an active BWP from BWP1 1010 to BWP2 1020 in response to anexpiry of BWP inactivity timer. For example, a UE may switch an activeBWP from BWP2 1020 to BWP3 1030 in response to receiving a DCIindicating BWP3 1030 as an active BWP. Switching an active BWP from BWP31030 to BWP2 1040 and/or from BWP2 1040 to BWP1 1050 may be in responseto receiving a DCI indicating an active BWP and/or in response to anexpiry of BWP inactivity timer.

In an example, if a UE is configured for a secondary cell with a defaultDL BWP among configured DL BWPs and a timer value, UE procedures on asecondary cell may be same as on a primary cell using the timer valuefor the secondary cell and the default DL BWP for the secondary cell.

In an example, if a base station configures a UE with a first active DLBWP and a first active UL BWP on a secondary cell or carrier, a UE mayemploy an indicated DL BWP and an indicated UL BWP on a secondary cellas a respective first active DL BWP and first active UL BWP on asecondary cell or carrier.

FIG. 11A and FIG. 11B show packet flows employing a multi connectivity(e.g. dual connectivity, multi connectivity, tight interworking, and/orthe like). FIG. 11A is an example diagram of a protocol structure of awireless device 110 (e.g. UE) with CA and/or multi connectivity as peran aspect of an embodiment. FIG. 11B is an example diagram of a protocolstructure of multiple base stations with CA and/or multi connectivity asper an aspect of an embodiment. The multiple base stations may comprisea master node, MN 1130 (e.g. a master node, a master base station, amaster gNB, a master eNB, and/or the like) and a secondary node, SN 1150(e.g. a secondary node, a secondary base station, a secondary gNB, asecondary eNB, and/or the like). A master node 1130 and a secondary node1150 may co-work to communicate with a wireless device 110.

When multi connectivity is configured for a wireless device 110, thewireless device 110, which may support multiple reception/transmissionfunctions in an RRC connected state, may be configured to utilize radioresources provided by multiple schedulers of a multiple base stations.Multiple base stations may be inter-connected via a non-ideal or idealbackhaul (e.g. Xn interface, X2 interface, and/or the like). A basestation involved in multi connectivity for a certain wireless device mayperform at least one of two different roles: a base station may eitheract as a master base station or as a secondary base station. In multiconnectivity, a wireless device may be connected to one master basestation and one or more secondary base stations. In an example, a masterbase station (e.g. the MN 1130) may provide a master cell group (MCG)comprising a primary cell and/or one or more secondary cells for awireless device (e.g. the wireless device 110). A secondary base station(e.g. the SN 1150) may provide a secondary cell group (SCG) comprising aprimary secondary cell (PSCell) and/or one or more secondary cells for awireless device (e.g. the wireless device 110).

In multi connectivity, a radio protocol architecture that a beareremploys may depend on how a bearer is setup. In an example, threedifferent type of bearer setup options may be supported: an MCG bearer,an SCG bearer, and/or a split bearer. A wireless device mayreceive/transmit packets of an MCG bearer via one or more cells of theMCG, and/or may receive/transmits packets of an SCG bearer via one ormore cells of an SCG. Multi-connectivity may also be described as havingat least one bearer configured to use radio resources provided by thesecondary base station. Multi-connectivity may or may not beconfigured/implemented in some of the example embodiments.

In an example, a wireless device (e.g. Wireless Device 110) may transmitand/or receive: packets of an MCG bearer via an SDAP layer (e.g. SDAP1110), a PDCP layer (e.g. NR PDCP 1111), an RLC layer (e.g. MN RLC1114), and a MAC layer (e.g. MN MAC 1118); packets of a split bearer viaan SDAP layer (e.g. SDAP 1110), a PDCP layer (e.g. NR PDCP 1112), one ofa master or secondary RLC layer (e.g. MN RLC 1115, SN RLC 1116), and oneof a master or secondary MAC layer (e.g. MN MAC 1118, SN MAC 1119);and/or packets of an SCG bearer via an SDAP layer (e.g. SDAP 1110), aPDCP layer (e.g. NR PDCP 1113), an RLC layer (e.g. SN RLC 1117), and aMAC layer (e.g. MN MAC 1119).

In an example, a master base station (e.g. MN 1130) and/or a secondarybase station (e.g. SN 1150) may transmit/receive: packets of an MCGbearer via a master or secondary node SDAP layer (e.g. SDAP 1120, SDAP1140), a master or secondary node PDCP layer (e.g. NR PDCP 1121, NR PDCP1142), a master node RLC layer (e.g. MN RLC 1124, MN RLC 1125), and amaster node MAC layer (e.g. MN MAC 1128); packets of an SCG bearer via amaster or secondary node SDAP layer (e.g. SDAP 1120, SDAP 1140), amaster or secondary node PDCP layer (e.g. NR PDCP 1122, NR PDCP 1143), asecondary node RLC layer (e.g. SN RLC 1146, SN RLC 1147), and asecondary node MAC layer (e.g. SN MAC 1148); packets of a split bearervia a master or secondary node SDAP layer (e.g. SDAP 1120, SDAP 1140), amaster or secondary node PDCP layer (e.g. NR PDCP 1123, NR PDCP 1141), amaster or secondary node RLC layer (e.g. MN RLC 1126, SN RLC 1144, SNRLC 1145, MN RLC 1127), and a master or secondary node MAC layer (e.g.MN MAC 1128, SN MAC 1148).

In multi connectivity, a wireless device may configure multiple MACentities: one MAC entity (e.g. MN MAC 1118) for a master base station,and other MAC entities (e.g. SN MAC 1119) for a secondary base station.In multi-connectivity, a configured set of serving cells for a wirelessdevice may comprise two subsets: an MCG comprising serving cells of amaster base station, and SCGs comprising serving cells of a secondarybase station. For an SCG, one or more of following configurations may beapplied: at least one cell of an SCG has a configured UL CC and at leastone cell of a SCG, named as primary secondary cell (PSCell, PCell ofSCG, or sometimes called PCell), is configured with PUCCH resources;when an SCG is configured, there may be at least one SCG bearer or oneSplit bearer; upon detection of a physical layer problem or a randomaccess problem on a PSCell, or a number of NR RLC retransmissions hasbeen reached associated with the SCG, or upon detection of an accessproblem on a PSCell during a SCG addition or a SCG change: an RRCconnection re-establishment procedure may not be triggered, ULtransmissions towards cells of an SCG may be stopped, a master basestation may be informed by a wireless device of a SCG failure type, forsplit bearer, a DL data transfer over a master base station may bemaintained; an NR RLC acknowledged mode (AM) bearer may be configuredfor a split bearer; PCell and/or PSCell may not be de-activated; PSCellmay be changed with a SCG change procedure (e.g. with security keychange and a RACH procedure); and/or a bearer type change between asplit bearer and a SCG bearer or simultaneous configuration of a SCG anda split bearer may or may not supported.

With respect to interaction between a master base station and asecondary base stations for multi-connectivity, one or more of thefollowing may be applied: a master base station and/or a secondary basestation may maintain RRM measurement configurations of a wirelessdevice; a master base station may (e.g. based on received measurementreports, traffic conditions, and/or bearer types) may decide to requesta secondary base station to provide additional resources (e.g. servingcells) for a wireless device; upon receiving a request from a masterbase station, a secondary base station may create/modify a containerthat may result in configuration of additional serving cells for awireless device (or decide that the secondary base station has noresource available to do so); for a UE capability coordination, a masterbase station may provide (a part of) an AS configuration and UEcapabilities to a secondary base station; a master base station and asecondary base station may exchange information about a UE configurationby employing of RRC containers (inter-node messages) carried via Xnmessages; a secondary base station may initiate a reconfiguration of thesecondary base station existing serving cells (e.g. PUCCH towards thesecondary base station); a secondary base station may decide which cellis a PSCell within a SCG; a master base station may or may not changecontent of RRC configurations provided by a secondary base station; incase of a SCG addition and/or a SCG SCell addition, a master basestation may provide recent (or the latest) measurement results for SCGcell(s); a master base station and secondary base stations may receiveinformation of SFN and/or subframe offset of each other from OAM and/orvia an Xn interface, (e.g. for a purpose of DRX alignment and/oridentification of a measurement gap). In an example, when adding a newSCG SCell, dedicated RRC signaling may be used for sending requiredsystem information of a cell as for CA, except for a SFN acquired from aMIB of a PSCell of a SCG.

FIG. 12 is an example diagram of a random access procedure. One or moreevents may trigger a random access procedure. For example, one or moreevents may be at least one of following: initial access from RRC_IDLE,RRC connection re-establishment procedure, handover, DL or UL dataarrival during RRC_CONNECTED when UL synchronization status isnon-synchronized, transition from RRC_Inactive, and/or request for othersystem information. For example, a PDCCH order, a MAC entity, and/or abeam failure indication may initiate a random access procedure.

In an example embodiment, a random access procedure may be at least oneof a contention based random access procedure and a contention freerandom access procedure. For example, a contention based random accessprocedure may comprise, one or more Msg 1 1220 transmissions, one ormore Msg2 1230 transmissions, one or more Msg3 1240 transmissions, andcontention resolution 1250. For example, a contention free random accessprocedure may comprise one or more Msg 1 1220 transmissions and one ormore Msg2 1230 transmissions.

In an example, a base station may transmit (e.g., unicast, multicast, orbroadcast), to a UE, a RACH configuration 1210 via one or more beams.The RACH configuration 1210 may comprise one or more parametersindicating at least one of following: available set of PRACH resourcesfor a transmission of a random access preamble, initial preamble power(e.g., random access preamble initial received target power), an RSRPthreshold for a selection of a SS block and corresponding PRACHresource, a power-ramping factor (e.g., random access preamble powerramping step), random access preamble index, a maximum number ofpreamble transmission, preamble group A and group B, a threshold (e.g.,message size) to determine the groups of random access preambles, a setof one or more random access preambles for system information requestand corresponding PRACH resource(s), if any, a set of one or more randomaccess preambles for beam failure recovery request and correspondingPRACH resource(s), if any, a time window to monitor RA response(s), atime window to monitor response(s) on beam failure recovery request,and/or a contention resolution timer.

In an example, the Msg1 1220 may be one or more transmissions of arandom access preamble. For a contention based random access procedure,a UE may select a SS block with a RSRP above the RSRP threshold. Ifrandom access preambles group B exists, a UE may select one or morerandom access preambles from a group A or a group B depending on apotential Msg3 1240 size. If a random access preambles group B does notexist, a UE may select the one or more random access preambles from agroup A. A UE may select a random access preamble index randomly (e.g.with equal probability or a normal distribution) from one or more randomaccess preambles associated with a selected group. If a base stationsemi-statistically configures a UE with an association between randomaccess preambles and SS blocks, the UE may select a random accesspreamble index randomly with equal probability from one or more randomaccess preambles associated with a selected SS block and a selectedgroup.

For example, a UE may initiate a contention free random access procedurebased on a beam failure indication from a lower layer. For example, abase station may semi-statistically configure a UE with one or morecontention free PRACH resources for beam failure recovery requestassociated with at least one of SS blocks and/or CSI-RS s. If at leastone of SS blocks with a RSRP above a first RSRP threshold amongstassociated SS blocks or at least one of CSI-RSs with a RSRP above asecond RSRP threshold amongst associated CSI-RSs is available, a UE mayselect a random access preamble index corresponding to a selected SSblock or CSI-RS from a set of one or more random access preambles forbeam failure recovery request.

For example, a UE may receive, from a base station, a random accesspreamble index via PDCCH or RRC for a contention free random accessprocedure. If a base station does not configure a UE with at least onecontention free PRACH resource associated with SS blocks or CSI-RS, theUE may select a random access preamble index. If a base stationconfigures a UE with one or more contention free PRACH resourcesassociated with SS blocks and at least one SS block with a RSRP above afirst RSRP threshold amongst associated SS blocks is available, the UEmay select the at least one SS block and select a random access preamblecorresponding to the at least one SS block. If a base station configuresa UE with one or more contention free PRACH resources associated withCSI-RSs and at least one CSI-RS with a RSRP above a second RSPRthreshold amongst the associated CSI-RSs is available, the UE may selectthe at least one CSI-RS and select a random access preamblecorresponding to the at least one CSI-RS.

A UE may perform one or more Msg1 1220 transmissions by transmitting theselected random access preamble. For example, if a UE selects an SSblock and is configured with an association between one or more PRACHoccasions and one or more SS blocks, the UE may determine an PRACHoccasion from one or more PRACH occasions corresponding to a selected SSblock. For example, if a UE selects a CSI-RS and is configured with anassociation between one or more PRACH occasions and one or more CSI-RSs, the UE may determine a PRACH occasion from one or more PRACHoccasions corresponding to a selected CSI-RS. A UE may transmit, to abase station, a selected random access preamble via a selected PRACHoccasions. A UE may determine a transmit power for a transmission of aselected random access preamble at least based on an initial preamblepower and a power-ramping factor. A UE may determine a RA-RNTIassociated with a selected PRACH occasions in which a selected randomaccess preamble is transmitted. For example, a UE may not determine aRA-RNTI for a beam failure recovery request. A UE may determine anRA-RNTI at least based on an index of a first OFDM symbol and an indexof a first slot of a selected PRACH occasions, and/or an uplink carrierindex for a transmission of Msg1 1220.

In an example, a UE may receive, from a base station, a random accessresponse, Msg 2 1230. A UE may start a time window (e.g., ra-ResponseWindow) to monitor a random access response. For beam failure recoveryrequest, a base station may configure a UE with a different time window(e.g., bfr-Response Window) to monitor response on beam failure recoveryrequest. For example, a UE may start a time window (e.g.,ra-ResponseWindow or bfr-Response Window) at a start of a first PDCCHoccasion after a fixed duration of one or more symbols from an end of apreamble transmission. If a UE transmits multiple preambles, the UE maystart a time window at a start of a first PDCCH occasion after a fixedduration of one or more symbols from an end of a first preambletransmission. A UE may monitor a PDCCH of a cell for at least one randomaccess response identified by a RA-RNTI or for at least one response tobeam failure recovery request identified by a C-RNTI while a timer for atime window is running.

In an example, a UE may consider a reception of random access responsesuccessful if at least one random access response comprises a randomaccess preamble identifier corresponding to a random access preambletransmitted by the UE. A UE may consider the contention free randomaccess procedure successfully completed if a reception of random accessresponse is successful. If a contention free random access procedure istriggered for a beam failure recovery request, a UE may consider acontention free random access procedure successfully complete if a PDCCHtransmission is addressed to a C-RNTI. In an example, if at least onerandom access response comprises a random access preamble identifier, aUE may consider the random access procedure successfully completed andmay indicate a reception of an acknowledgement for a system informationrequest to upper layers. If a UE has signaled multiple preambletransmissions, the UE may stop transmitting remaining preambles (if any)in response to a successful reception of a corresponding random accessresponse.

In an example, a UE may perform one or more Msg 3 1240 transmissions inresponse to a successful reception of random access response (e.g., fora contention based random access procedure). A UE may adjust an uplinktransmission timing based on a timing advanced command indicated by arandom access response and may transmit one or more transport blocksbased on an uplink grant indicated by a random access response.Subcarrier spacing for PUSCH transmission for Msg3 1240 may be providedby at least one higher layer (e.g. RRC) parameter. A UE may transmit arandom access preamble via PRACH and Msg3 1240 via PUSCH on a same cell.A base station may indicate an UL BWP for a PUSCH transmission of Msg31240 via system information block. A UE may employ HARQ for aretransmission of Msg 3 1240.

In an example, multiple UEs may perform Msg 1 1220 by transmitting asame preamble to a base station and receive, from the base station, asame random access response comprising an identity (e.g., TC-RNTI).Contention resolution 1250 may ensure that a UE does not incorrectly usean identity of another UE. For example, contention resolution 1250 maybe based on C-RNTI on PDCCH or a UE contention resolution identity onDL-SCH. For example, if a base station assigns a C-RNTI to a UE, the UEmay perform contention resolution 1250 based on a reception of a PDCCHtransmission that is addressed to the C-RNTI. In response to detectionof a C-RNTI on a PDCCH, a UE may consider contention resolution 1250successful and may consider a random access procedure successfullycompleted. If a UE has no valid C-RNTI, a contention resolution may beaddressed by employing a TC-RNTI. For example, if a MAC PDU issuccessfully decoded and a MAC PDU comprises a UE contention resolutionidentity MAC CE that matches the CCCH SDU transmitted in Msg3 1250, a UEmay consider the contention resolution 1250 successful and may considerthe random access procedure successfully completed.

FIG. 13 is an example structure for MAC entities as per an aspect of anembodiment. In an example, a wireless device may be configured tooperate in a multi-connectivity mode. A wireless device in RRC_CONNECTEDwith multiple RX/TX may be configured to utilize radio resourcesprovided by multiple schedulers located in a plurality of base stations.The plurality of base stations may be connected via a non-ideal or idealbackhaul over the Xn interface. In an example, a base station in aplurality of base stations may act as a master base station or as asecondary base station. A wireless device may be connected to one masterbase station and one or more secondary base stations. A wireless devicemay be configured with multiple MAC entities, e.g. one MAC entity formaster base station, and one or more other MAC entities for secondarybase station(s). In an example, a configured set of serving cells for awireless device may comprise two subsets: an MCG comprising servingcells of a master base station, and one or more SCGs comprising servingcells of a secondary base station(s). FIG. 13 illustrates an examplestructure for MAC entities when MCG and SCG are configured for awireless device.

In an example, at least one cell in a SCG may have a configured UL CC,wherein a cell of at least one cell may be called PSCell or PCell ofSCG, or sometimes may be simply called PCell. A PSCell may be configuredwith PUCCH resources. In an example, when a SCG is configured, there maybe at least one SCG bearer or one split bearer. In an example, upondetection of a physical layer problem or a random access problem on aPSCell, or upon reaching a number of RLC retransmissions associated withthe SCG, or upon detection of an access problem on a PSCell during a SCGaddition or a SCG change: an RRC connection re-establishment proceduremay not be triggered, UL transmissions towards cells of an SCG may bestopped, a master base station may be informed by a UE of a SCG failuretype and DL data transfer over a master base station may be maintained.

In an example, a MAC sublayer may provide services such as data transferand radio resource allocation to upper layers (e.g. 1310 or 1320). A MACsublayer may comprise a plurality of MAC entities (e.g. 1350 and 1360).A MAC sublayer may provide data transfer services on logical channels.To accommodate different kinds of data transfer services, multiple typesof logical channels may be defined. A logical channel may supporttransfer of a particular type of information. A logical channel type maybe defined by what type of information (e.g., control or data) istransferred. For example, BCCH, PCCH, CCCH and DCCH may be controlchannels and DTCH may be a traffic channel. In an example, a first MACentity (e.g. 1310) may provide services on PCCH, BCCH, CCCH, DCCH, DTCHand MAC control elements. In an example, a second MAC entity (e.g. 1320)may provide services on BCCH, DCCH, DTCH and MAC control elements.

A MAC sublayer may expect from a physical layer (e.g. 1330 or 1340)services such as data transfer services, signaling of HARQ feedback,signaling of scheduling request or measurements (e.g. CQI). In anexample, in dual connectivity, two MAC entities may be configured for awireless device: one for MCG and one for SCG. A MAC entity of wirelessdevice may handle a plurality of transport channels. In an example, afirst MAC entity may handle first transport channels comprising a PCCHof MCG, a first BCH of MCG, one or more first DL-SCHs of MCG, one ormore first UL-SCHs of MCG and one or more first RACHs of MCG. In anexample, a second MAC entity may handle second transport channelscomprising a second BCH of SCG, one or more second DL-SCHs of SCG, oneor more second UL-SCHs of SCG and one or more second RACHs of SCG.

In an example, if a MAC entity is configured with one or more SCells,there may be multiple DL-SCHs and there may be multiple UL-SCHs as wellas multiple RACHs per MAC entity. In an example, there may be one DL-SCHand UL-SCH on a SpCell. In an example, there may be one DL-SCH, zero orone UL-SCH and zero or one RACH for an SCell. A DL-SCH may supportreceptions using different numerologies and/or TTI duration within a MACentity. A UL-SCH may also support transmissions using differentnumerologies and/or TTI duration within the MAC entity.

In an example, a MAC sublayer may support different functions and maycontrol these functions with a control (e.g. 1355 or 1365) element.Functions performed by a MAC entity may comprise mapping between logicalchannels and transport channels (e.g., in uplink or downlink),multiplexing (e.g. 1352 or 1362) of MAC SDUs from one or differentlogical channels onto transport blocks (TB) to be delivered to thephysical layer on transport channels (e.g., in uplink), demultiplexing(e.g. 1352 or 1362) of MAC SDUs to one or different logical channelsfrom transport blocks (TB) delivered from the physical layer ontransport channels (e.g., in downlink), scheduling information reporting(e.g., in uplink), error correction through HARQ in uplink or downlink(e.g. 1363), and logical channel prioritization in uplink (e.g. 1351 or1361). A MAC entity may handle a random access process (e.g. 1354 or1364).

FIG. 14 is an example diagram of a RAN architecture comprising one ormore base stations. In an example, a protocol stack (e.g. RRC, SDAP,PDCP, RLC, MAC, and PHY) may be supported at a node. A base station(e.g. 120A or 120B) may comprise a base station central unit (CU) (e.g.gNB-CU 1420A or 1420B) and at least one base station distributed unit(DU) (e.g. gNB-DU 1430A, 1430B, 1430C, or 1430D) if a functional splitis configured. Upper protocol layers of a base station may be located ina base station CU, and lower layers of the base station may be locatedin the base station DUs. An F1 interface (e.g. CU-DU interface)connecting a base station CU and base station DUs may be an ideal ornon-ideal backhaul. F1-C may provide a control plane connection over anF1 interface, and F1-U may provide a user plane connection over the F1interface. In an example, an Xn interface may be configured between basestation CUs.

In an example, a base station CU may comprise an RRC function, an SDAPlayer, and a PDCP layer, and base station DUs may comprise an RLC layer,a MAC layer, and a PHY layer. In an example, various functional splitoptions between a base station CU and base station DUs may be possibleby locating different combinations of upper protocol layers (RANfunctions) in a base station CU and different combinations of lowerprotocol layers (RAN functions) in base station DUs. A functional splitmay support flexibility to move protocol layers between a base stationCU and base station DUs depending on service requirements and/or networkenvironments.

In an example, functional split options may be configured per basestation, per base station CU, per base station DU, per UE, per bearer,per slice, or with other granularities. In per base station CU split, abase station CU may have a fixed split option, and base station DUs maybe configured to match a split option of a base station CU. In per basestation DU split, a base station DU may be configured with a differentsplit option, and a base station CU may provide different split optionsfor different base station DUs. In per UE split, a base station (basestation CU and at least one base station DUs) may provide differentsplit options for different wireless devices. In per bearer split,different split options may be utilized for different bearers. In perslice splice, different split options may be applied for differentslices.

FIG. 15 is an example diagram showing RRC state transitions of awireless device. In an example, a wireless device may be in at least oneRRC state among an RRC connected state (e.g. RRC Connected 1530,RRC_Connected), an RRC idle state (e.g. RRC Idle 1510, RRC_Idle), and/oran RRC inactive state (e.g. RRC_Inactive 1520, RRC_Inactive). In anexample, in an RRC connected state, a wireless device may have at leastone RRC connection with at least one base station (e.g. gNB and/or eNB),which may have a UE context of the wireless device. A UE context (e.g. awireless device context) may comprise at least one of an access stratumcontext, one or more radio link configuration parameters, bearer (e.g.data radio bearer (DRB), signaling radio bearer (SRB), logical channel,QoS flow, PDU session, and/or the like) configuration information,security information, PHY/MAC/RLC/PDCP/SDAP layer configurationinformation, and/or the like configuration information for a wirelessdevice. In an example, in an RRC idle state, a wireless device may nothave an RRC connection with a base station, and a UE context of awireless device may not be stored in a base station. In an example, inan RRC inactive state, a wireless device may not have an RRC connectionwith a base station. A UE context of a wireless device may be stored ina base station, which may be called as an anchor base station (e.g. lastserving base station).

In an example, a wireless device may transition a UE RRC state betweenan RRC idle state and an RRC connected state in both ways (e.g.connection release 1540 or connection establishment 1550; or connectionreestablishment) and/or between an RRC inactive state and an RRCconnected state in both ways (e.g. connection inactivation 1570 orconnection resume 1580). In an example, a wireless device may transitionits RRC state from an RRC inactive state to an RRC idle state (e.g.connection release 1560).

In an example, an anchor base station may be a base station that maykeep a UE context (a wireless device context) of a wireless device atleast during a time period that a wireless device stays in a RANnotification area (RNA) of an anchor base station, and/or that awireless device stays in an RRC inactive state. In an example, an anchorbase station may be a base station that a wireless device in an RRCinactive state was lastly connected to in a latest RRC connected stateor that a wireless device lastly performed an RNA update procedure in.In an example, an RNA may comprise one or more cells operated by one ormore base stations. In an example, a base station may belong to one ormore RNAs. In an example, a cell may belong to one or more RNAs.

In an example, a wireless device may transition a UE RRC state from anRRC connected state to an RRC inactive state in a base station. Awireless device may receive RNA information from the base station. RNAinformation may comprise at least one of an RNA identifier, one or morecell identifiers of one or more cells of an RNA, a base stationidentifier, an IP address of the base station, an AS context identifierof the wireless device, a resume identifier, and/or the like.

In an example, an anchor base station may broadcast a message (e.g. RANpaging message) to base stations of an RNA to reach to a wireless devicein an RRC inactive state, and/or the base stations receiving the messagefrom the anchor base station may broadcast and/or multicast anothermessage (e.g. paging message) to wireless devices in their coveragearea, cell coverage area, and/or beam coverage area associated with theRNA through an air interface.

In an example, when a wireless device in an RRC inactive state movesinto a new RNA, the wireless device may perform an RNA update (RNAU)procedure, which may comprise a random access procedure by the wirelessdevice and/or a UE context retrieve procedure. A UE context retrieve maycomprise: receiving, by a base station from a wireless device, a randomaccess preamble; and fetching, by a base station, a UE context of thewireless device from an old anchor base station. Fetching may comprise:sending a retrieve UE context request message comprising a resumeidentifier to the old anchor base station and receiving a retrieve UEcontext response message comprising the UE context of the wirelessdevice from the old anchor base station.

In an example embodiment, a wireless device in an RRC inactive state mayselect a cell to camp on based on at least a on measurement results forone or more cells, a cell where a wireless device may monitor an RNApaging message and/or a core network paging message from a base station.In an example, a wireless device in an RRC inactive state may select acell to perform a random access procedure to resume an RRC connectionand/or to transmit one or more packets to a base station (e.g. to anetwork). In an example, if a cell selected belongs to a different RNAfrom an RNA for a wireless device in an RRC inactive state, the wirelessdevice may initiate a random access procedure to perform an RNA updateprocedure. In an example, if a wireless device in an RRC inactive statehas one or more packets, in a buffer, to transmit to a network, thewireless device may initiate a random access procedure to transmit oneor more packets to a base station of a cell that the wireless deviceselects. A random access procedure may be performed with two messages(e.g. 2 stage random access) and/or four messages (e.g. 4 stage randomaccess) between the wireless device and the base station.

In an example embodiment, a base station receiving one or more uplinkpackets from a wireless device in an RRC inactive state may fetch a UEcontext of a wireless device by transmitting a retrieve UE contextrequest message for the wireless device to an anchor base station of thewireless device based on at least one of an AS context identifier, anRNA identifier, a base station identifier, a resume identifier, and/or acell identifier received from the wireless device. In response tofetching a UE context, a base station may transmit a path switch requestfor a wireless device to a core network entity (e.g. AMF, MME, and/orthe like). A core network entity may update a downlink tunnel endpointidentifier for one or more bearers established for the wireless devicebetween a user plane core network entity (e.g. UPF, S-GW, and/or thelike) and a RAN node (e.g. the base station), e.g. changing a downlinktunnel endpoint identifier from an address of the anchor base station toan address of the base station.

A gNB may communicate with a wireless device via a wireless networkemploying one or more new radio technologies. The one or more radiotechnologies may comprise at least one of: multiple technologies relatedto physical layer; multiple technologies related to medium accesscontrol layer; and/or multiple technologies related to radio resourcecontrol layer. Example embodiments of enhancing the one or more radiotechnologies may improve performance of a wireless network. Exampleembodiments may increase the system throughput, or data rate oftransmission. Example embodiments may reduce battery consumption of awireless device. Example embodiments may improve latency of datatransmission between a gNB and a wireless device. Example embodimentsmay improve network coverage of a wireless network. Example embodimentsmay improve transmission efficiency of a wireless network.

In an example, there may be many network-sharing scenarios depending ondifferent operator strategies but also on rules and legislation indifferent countries. The equivalent PLMN feature may allow operators toshare a common base station, with certain parts of the core networksshared between the operators.

In an example, network-sharing scenario may allow operators to share thenetwork and/or supply its customers with wireless services. For example,an operator may supply its subscribers with services using anotheroperator's allocated spectrum. A geographically split network, e.g. ascenario in which cooperating operators cover different parts of acountry, may be possible. One operator's core network may also beconnected to several base stations.

In an example, it may not only the sharing solution at a certain timethat is important, but also how it is possible for the sharing partnersto evolve either to a more dedicated network or to a more joint network.A set of infrastructure sharing solutions and scenarios that isdiscussed in the industry may cover alternatives that together comprise:solution alternatives targeting at dedicated networks in the nearfuture; solutions for infrastructure sharing not targeting at immediateexit, but at exit when for example the network capacity demand sorequires; and/or infrastructure sharing targeting at long term sharing,which for example may be the case when one of the operators lacks afrequency license. In an example, identifying, changing, and addingappropriate functionality in the network may lead to a bettershared-network operation.

In an example, for operators that have multiple frequency allocations itmay be possible to share the RAN elements, but not to share the radiofrequencies. In this case the operators may connect directly to theirown dedicated carrier layer in the shared base station.

In an example, in this scenario, two (or more) operators with individuallicenses may with their respective radio access networks cover differentparts of a country but together provide coverage of the entire country.

In an example, when two (or more operators) employ national roaming forthe users (e.g. UEs), which may imply that one core network may beassociated with radio access network. Care may be needed when coverageregions overlap, which may make this a valid shared-networks scenario.

In an example, the operators may have their individual core networksconnected to both radio access networks throughout the entire coveragearea, e.g. utilizing the different operator's allocated spectrum indifferent parts of the coverage area. There may be multiple core networkoperators in the shared radio access networks. The connection of thecore networks to the radio access networks (e.g. base stations) mayeither be done by connecting the radio network controllers to bothoperators' core network elements or by sharing parts of the corenetwork. It may be possible to introduce interface flex functionalitybetween the common core network parts and the radio access network forpurely load-sharing purposes.

In an example, in areas where more than one of the operators providecoverage, it may be possible to restrict the access rights so that theusers may be allowed to use the radio access network provided by theirhome operator.

In an example, one operator may deploy coverage in a specificgeographical area, and other operators may be allowed to use thiscoverage for their subscribers. Outside this geographical area, coveragemay be provided by the operators.

For example, in the case of two operators, a third-party could provideRAN coverage to operators A and B′ subscribers in areas with highpopulation density. In less dense areas, other RAN coverage is providedby operator A and operator B and in these areas the subscribers mayconnect to the access network of their operator.

In an example, common spectrum network sharing may be applicable when:one operator has a license and/or shares the allocated spectrum withother operators; and/or a number of operators decide to pool theirallocated spectrums and share the total spectrum (operators withoutallocated spectrum may also share this pooled spectrum).

In an example, connecting operator's core networks and/or the sharedradio access network(s) (1 radio network controller for simplicity). Inthis case, it may be possible that one or more of the core networkoperators use interface Flex between their core network and the sharedradio access network. Operators A and C may not be using multiple corenetwork nodes (CN) and therefore may not need to use interface flex.Operator B may be using multiple CNs and/or may have decided to useinterface flex to enable the intra-domain sharing of CNs.

In an example, the core network entities connected to radio accessnetwork may be shared. The work on shared networks may be the choice ofthe operator which one is implemented.

In network sharing scenario multiple radio access networks may share acommon network. The multiple RANs may belong to different PLMNs andnetwork operators. Due to operators' deployment different nodes or partof the common core network may be shared.

In an example, to fully support for handover, service differentiationand access rights in shared networks, it may be necessary to identify towhich operator that a user (e.g. UE) belongs to and possibly group theusers according to this information. To avoid complicated operation andmaintenance procedures, such user classification may be general for thefunctions in the shared network that needs information about the useridentity. Network sharing may be an agreement between network operatorsand/or may be transparent to the user.

In an example, when network sharing exists between different operatorsand a user roams into the shared network, it may be possible for thatuser to register with a core network operator (among the network sharingpartners) that either: the user has a subscription with; or the user'shome operator has a roaming agreement with, even if the operator is notoffering radio coverage. The selection of a core network operator amongthose connected to the shared radio access network may either be manual(i.e. performed by the user after receiving a list of available corenetwork operators) or automatic (i.e. performed by the UE according touser and operator preferred settings).

In an example, the terminal may display the name of the core networkoperator (e.g. PLMN) that the user has registered with. A networksharing solution may support legacy UEs. In an example, the followingtwo cases may be identified: Manual network selection for roaming users;and/or Network name display for roaming users. The service capabilitiesand requirements may not be restricted by network sharing scenarios. Itmay be possible for a network operator to differentiate its serviceoffering from other network operators within shared network.

In an example, the services and service capabilities offered may not berestricted by the existence of network sharing. It may be possible for anetwork operator to differentiate its service offering from othernetwork operators within shared network. The provision of services andservice capabilities that is possible to offer in a network may not berestricted by the existence of the network sharing It may be possiblefor a core network operator to differentiate its service offering fromother core network operators within the shared network. It may bepossible to control the access to service capabilities offered by ashared network according to the core network operator the user issubscribed to. The mobility in a shared network, both when controlled bythe UE and when controlled by the network may not cause undueinterruption of service.

In an example, it may be possible for a subscriber to roam between thedifferent parts of a shared network without requiring the userintervention. The user experience while roaming in a shared network maybe no worse than the user experiences in a non-shared network. In someinstances, the user intervention may be required, for example it may berequired in cases where the change to a different part of the sharednetwork causes a change in the service tariff.

In an example, seamless handover may be supported between a sharednetwork and a non-shared network. The user (e.g. UE) may be able toreceive the same service level during and after a handover between thenetworks.

In an example, the network may be able to access the relevant subscriberinformation in order to determine the appropriate candidate forhandover. Examples of information that may be required in order to takethe decision on the candidate could include (non-exhaustive list): typeof subscription (e.g. prepay/postpay); home network of the subscriber(for roaming subscribers); service(s) to be handed over; subscribedquality of service.

In an example, when the user is registered on a shared network, thecontrol of the PLMN and radio access technology employed within thatshared network is under the sole control of the network operator. Thismay not imply any limitation on the manual or automatic selection of aPLMN that does not belong to the shared network where the user isregistered.

In an example, the standards may specify mechanisms necessary to enableflexible allocation of inbound roamers among core network operators thathave roaming agreements with the same roaming partners. The core networkoperators may be able to pre-define their relative share of inboundroamers and the network may distribute the inbound roamers that applyautomatic network selection to different core networks connected to theradio access network accordingly. It may also be possible for the corenetwork operator to allow or force the subscribers to reselect toanother part of the shared network so that the relative share of inboundroamers is maintained.

In an example, in case the mobility in the shared network is controlledby the UE (e.g. cell reselection) the operator may be able to setparameters, other than radio parameters that determine the mostappropriate candidate. Examples of these parameters are: subscriptioninformation, requested service, network load and so on. Chargingsolutions may support the shared network architecture so that both endusers and network sharing partners may be correctly charged for theirusage of the shared network.

In an example, a UE may apply a system information acquisition procedureto acquire AS- and/or NAS-system information that may be broadcasted byE-UTRAN and/or net radio (NR). Procedures may apply to UEs in RRC_IDLE,RRC_INACTIVE, and/or in RRC_CONNECTED.

In an example, a UE may apply a system information acquisition procedureupon selecting (e.g. upon power on) and/or upon re-selecting a cell,after handover completion, after entering E-UTRA/NR from another radioaccess technology (RAT), upon return from out of coverage, uponreceiving a notification that system information has changed, uponreceiving an indication about a presence of an ETWS notification, uponreceiving an indication about a presence of a CMAS notification, uponreceiving a notification that a EAB parameters have changed, uponreceiving a request from CDMA2000 upper layers and/or upon exceeding amaximum validity duration. In an example, a system informationacquisition procedure may overwrite stored system information, e.g.delta configuration may not be applicable for system information and/ora UE discontinues using a field if it is absent in system informationunless explicitly specified otherwise.

In an example, in RRC_CONNECTED, BL UEs and/or UEs in CE may be requiredto acquire system information when T311 is running and/or upon handoverwhere a UE may be required to acquire a MasterinformationBlock in atarget PCell. Upon handover, E-UTRAN/NR may provide system informationrequired by a UE in RRC_CONNECTED (e.g. except MIB) with RRC signalling,e.g. systemInformationBlockType1Dedicated and/or mobilityControlInfo.

In an example, a UE may: 1> ensure having a valid version, as definedbelow, of (at least) a following system information, also referred to asa ‘required’ system information: 2> if in RRC_IDLE/RRC_INACTIVE: 3> if aUE is a NB-IoT UE: 4> a MasterinformationBlock-NB andSystemInformationBlockType1-NB as well as SystemInformationBlockType2-NBthrough SystemInformationBlockType5-NB, SystemInformationBlockType22-NB;3> else: 4> a MasterInformationBlock and/or SystemInformationBlockType1(or SystemInformationBlockType1-BR depending on whether a UE is a BL UEor a UE in CE) as well as SystemInformationBlockType2 throughSystemInformationBlockType8 (depending on support of a concerned RATs),SystemInformationBlockType17 (depending on support of RAN-assisted WLANinterworking); 2> if in RRC_CONNECTED; and/or 2> a UE is not a BL UE;and/or 2> a UE is not in CE; and/or 2> a UE is not a NB-IoT UE: 3> aMasterInformationBlock, SystemInformationBlockType1 and/orSystemInformationBlockType2 as well as SystemInformationBlockType8(depending on support of CDMA2000), SystemInformationBlockType17(depending on support of RAN-assisted WLAN interworking); 2> if inRRC_CONNECTED and/or T311 is running; and/or 2> a UE is a BL UE or a UEis in CE or a UE is a NB-IoT UE; 3> a MasterinformationBlock (orMasterinformationBlock-NB in NB-IoT), SystemInformationBlockType1-BR (orSystemInformationBlockType1-NB in NB-IoT) and/orSystemInformationBlockType2 (or SystemInformationBlockType2-NB inNB-IoT), and/or for NB-IoT SystemInformationBlockType22-NB; 1> deletestored system information after 3 hours or 24 hours from a moment it wasconfirmed to be valid, unless specified otherwise; 1> consider storedsystem information except SystemInformationBlockType10,SystemInformationBlockType11, systemInformationBlockType12 and/orsystemInformationBlockType14 (systemInformationBlockType14-NB in NB-IoT)to be invalid if systemInfoValueTag included inSystemInformationBlockType1 (MasterinformationBlock-NB in NB-IoT) may bedifferent from one of stored system information and/or in case of NB-IoTUEs, BL UEs and UEs in CE, systemInfoValueTagSI is not broadcasted;

In an example, a UE may: 1> apply a specified BCCH configuration orBR-BCCH configuration; 1> if a procedure is triggered by a systeminformation change notification: 2> if a UE uses an idle/inactive DRXcycle longer than a modification period: 3> start acquiring requiredsystem information from a next eDRX acquisition period boundary; 2> else3> start acquiring a required system information from a beginning of amodification period following one in which a change notification wasreceived; (a UE may continue using previously received systeminformation until new system information has been acquired) 1> if a UEis in RRC_IDLE/RRC_INACTIVE and/or enters a cell for which a UE does nothave stored a valid version of system information required inRRC_IDLE/RRC_INACTIVE: 2> acquire, using a system informationacquisition procedure, system information required inRRC_IDLE/RRC_INACTIVE; 1> following successful handover completion to aPCell for which a UE does not have stored a valid version of systeminformation required in RRC_CONNECTED: 2> acquire, using a systeminformation acquisition procedure, system information required inRRC_CONNECTED; 2> upon acquiring concerned system information: 3>discard corresponding radio resource configuration information includedin a radioResourceConfigCommon previously received in a dedicatedmessage, if any; 1> following a request from CDMA2000 upper layers: 2>acquire SystemInformationBlockType8; 1> neither initiate an RRCconnection establishment/resume procedure nor initiate transmission ofan RRCConnectionReestablishmentRequest message until a UE has a validversion of a MasterInformationBlock (MasterInformationBlock-NB inNB-IoT) and/or SystemInformationBlockType1(SystemInformationBlockType1-NB in NB-IoT) messages as well asSystemInformationBlockType2 (SystemInformationBlockType2-NB in NB-IoT),and/or for NB-IoT, SystemInformationBlockType22-NB; 1> not initiate anRRC connection establishment/resume procedure subject to EAB until a UEhas a valid version of SystemInformationBlockType14, if broadcast; 1> ifa UE is ETWS capable: 2> upon entering a cell duringRRC_IDLE/RRC_INACTIVE, following successful handover or upon connectionre-establishment: 3> discard previously buffered warningMessageSegment;3> clear, if any, a current values of messageldentifier and serialNumberfor SystemInformationBlockType11; 2> when a UE acquiresSystemInformationBlockType1 following ETWS indication, upon entering acell during RRC_IDLE, following successful handover or upon connectionre-establishment: 3> if schedulingInfoList indicates thatSystemInformationBlockType10 is present: 4> if a UE is in CE: 5> startacquiring SystemInformationBlockType10; 4> else 5> start acquiringSystemInformationBlockType10 immediately; 3> if schedulingInfoListindicates that SystemInformationBlockType1l is present: 4> startacquiring SystemInformationBlockType1l immediately; (UEs may startacquiring SystemInformationBlockType10 and SystemInformationBlockType1las described above even when systemInfoValueTag inSystemInformationBlockType1 has not changed)

1> if a UE is CMAS capable: 2> upon entering a cell duringRRC_IDLE/RRC_INACTIVE, following successful handover or upon connectionre-establishment: 3> discard previously buffered warningMessageSegment;3> clear, if any, stored values of messageldentifier and serialNumberfor SystemInformationBlockType12 associated with a discardedwarningMessageSegment; 2> when a UE acquires SystemInformationBlockType1following CMAS indication, upon entering a cell duringRRC_IDLE/RRC_INACTIVE, following successful handover and upon connectionre-establishment: 3> if schedulingInfoList indicates thatSystemInformationBlockType12 is present: 4> acquireSystemInformationBlockType12; (UEs may start acquiringSystemInformationBlockType12 as described above even whensystemInfoValueTag in SystemInformationBlockType1 has not changed)

1> if a UE is interested to receive MBMS services: 2> if a UE is capableof MBMS reception: 3> if schedulingInfoList indicates thatSystemInformationBlockType13 is present and a UE does not have stored avalid version of this system information block: 4> acquireSystemInformationBlockType13; 3> else if SystemInformationBlockType13 ispresent in SystemInformationBlockType1-MBMS and a UE does not havestored a valid version of this system information block: 4> acquireSystemInformationBlockType13 from SystemInformationBlockType1-MBMS; 2>if a UE is capable of SC-PTM reception: 3> if schedulingInfoListindicates that SystemInformationBlockType20(SystemInformationBlockType20-NB in NB-IoT) is present and/or a UE doesnot have stored a valid version of this system information block: 4>acquire SystemInformationBlockType20 (SystemInformationBlockType20-NB inNB-IoT); 2> if a UE is capable of MBMS Service Continuity: 3> ifschedulingInfoList indicates that SystemInformationBlockType15(SystemInformationBlockType15-NB in NB-IoT) is present and/or a UE doesnot have stored a valid version of this system information block: 4>acquire SystemInformationBlockType15 (SystemInformationBlockType15-NB inNB-IoT);

1> if a UE is EAB capable: 2> when a UE does not have stored a validversion of SystemInformationBlockType14 upon enteringRRC_IDLE/RRC_INACTIVE, and/or when a UE acquiresSystemInformationBlockType1 following EAB parameters changenotification, and/or upon entering a cell during RRC_IDLE/RRC_INACTIVE,or before establishing an RRC connection if using eDRX with DRX cyclelonger than a modification period: 3> if schedulingInfoList indicatesthat SystemInformationBlockType14 is present: 4> start acquiringSystemInformationBlockType14 immediately; 3> else: 4> discardSystemInformationBlockType14, if previously received; (EAB capable UEsmay start acquiring SystemInformationBlockType14 as described above evenwhen systemInfoValueTag in SystemInformationBlockType1 has not changed)(EAB capable UEs may maintain an up to date SystemInformationBlockType14in RRC_IDLE/RRC_INACTIVE)

1> if a UE is capable of sidelink communication and/or is configured byupper layers to receive or transmit sidelink communication: 2> if a cellused for sidelink communication meets an S-criteria; and/or 2> ifschedulingInfoList indicates that SystemInformationBlockType18 ispresent and/or a UE does not have stored a valid version of this systeminformation block: 3> acquire SystemInformationBlockType18; 1> if a UEis capable of sidelink discovery and/or is configured by upper layers toreceive or transmit sidelink discovery announcements on a primaryfrequency: 2> if schedulingInfoList of a serving cell/PCell indicatesthat SystemInformationBlockType19 is present and/or a UE does not havestored a valid version of this system information block: 3> acquireSystemInformationBlockType19; 1> if a UE is capable of sidelinkdiscovery and/or, for one or more frequencies included indiscInterFreqList, if included in SystemInformationBlockType19 and/orfor which a UE is configured by upper layers to receive sidelinkdiscovery announcements on: 2> if SystemInformationBlockType19 of aserving cell/PCell does not provide corresponding reception resources;and/or 2> if schedulingInfoList of a cell on a concerned frequencyindicates that SystemInformationBlockType19 is present and/or a UE doesnot have stored a valid version of this system information block: 3>acquire SystemInformationBlockType19; 1> if a UE is capable of sidelinkdiscovery and/or, for one or more frequencies included indiscInterFreqList, if included in SystemInformationBlockType19 and/orfor which a UE is configured by upper layers to transmit sidelinkdiscovery announcements on: 2> if SystemInformationBlockType19 of aserving cell/PCell includes discTxResourcesInterFreq which may be set toacquireSI-FromCarrier; and/or 2> if schedulingInfoList of a cell on aconcerned frequency indicates that SystemInformationBlockType19 ispresent and a UE does not have stored a valid version of this systeminformation block: 3> acquire SystemInformationBlockType19; 1> if a UEis a NB-IoT UE and/or if ab-Enabled included inMasterInformationBlock-NB is set to TRUE: 2> not initiate a RRCconnection establishment/resume procedure for access causes (e.g. exceptmobile terminating calls) until a UE has acquired aSystemInformationBlockType14-NB; 1> if a UE is capable of V2X sidelinkcommunication and/or is configured by upper layers to receive ortransmit V2X sidelink communication on a frequency: 2> ifschedulingInfoList on a serving cell/PCell indicates thatSystemInformationBlockType21 is present and/or a UE does not have storedvalid version of this system information block; 3> acquireSystemInformationBlockType21 from serving cell/PCell; 1> if a UE iscapable of V2X sidelink communication and is configured by upper layersto receive V2X sidelink communication on a frequency, which may not beprimary frequency: 2> if SystemInformationBlockType21 of a servingcell/PCell does not provide reception resource pool for V2X sidelinkcommunication for a concerned frequency; and/or 2> if a cell used forV2X sidelink communication on a concerned frequency meets an S-criteria;and/or 2> if schedulingInfoList on a concerned frequency indicates thatSystemInformationBlockType21 is present and a UE does not have stored avalid version of this system information block: 3> acquireSystemInformationBlockType21 from a concerned frequency; 1> if a UE iscapable of V2X sidelink communication and/or is configured by upperlayers to transmit V2X sidelink communication on a frequency, which maynot primary frequency and/or may not be included inv2x-InterFreqInfoList in SystemInformationBlockType21 of a servingcell/PCell: 2> if a cell used for V2X sidelink communication on aconcerned frequency meets an S-criteria; and/or 2> if schedulingInfoListon a concerned frequency indicates that SystemInformationBlockType21 ispresent and/or a UE does not have stored a valid version of this systeminformation block: 3> acquire SystemInformationBlockType21 from aconcerned frequency; a UE may apply received SIBs immediately, e.g. a UEmay not need to delay using a SIB until SI messages have been received.A UE may delay applying received SIBs until completing lower layerprocedures associated with a received and/or a UE originated RRCmessage, e.g. an ongoing random access procedure. While attempting toacquire a particular SIB, if a UE detects from schedulingInfoList thatit may be no longer present, a UE may stop trying to acquire aparticular SIB.

In an example, a UE may: 1> if in RRC_IDLE/RRC_INACTIVE or inRRC_CONNECTED while T311 is running: 2> if a UE is unable to acquire aMasterInformationBlock (MasterInformationBlock-NB in NB-IoT); and/or 2>if a UE is neither a BL UE nor in CE nor in NB-IoT and a UE is unable toacquire a SystemInformationBlockType1; and/or 2> if a BL UE or UE in CEis unable to acquire SystemInformationBlockType1-BR and/orSystemInformationBlockType1-BR is not scheduled; and/or 2> if a NB-IoTUE is unable to acquire a SystemInformationBlockType1-NB: 3> consider acell as barred; and/or 3> perform barring as if intraFreqReselection isset to allowed, and/or as if a csg-Indication is set to FALSE; 2> elseif a UE is unable to acquire a SystemInformationBlockType2 (orSystemInformationBlockType2-NB in NB-IoT) and/or for NB-IoT,SystemInformationBlockType22-NB if scheduled: 3> treat a cell as barred.

In an example, upon receiving a MasterinformationBlock message, a UEmay: 1> apply a radio resource configuration included in a phich-Config;1> if a UE is in RRC_IDLE/RRC_INACTIVE or if a UE is in RRC_CONNECTEDwhile T311 is running: 2> if a UE has no valid system information storedfor a concerned cell: 3> apply a received value of dl-Bandwidth to aul-Bandwidth until SystemInformationBlockType2 is received. In anexample, upon receiving a MasterinformationBlock-NB message, a UE may:1> apply a radio resource configuration included in accordance with anoperationModeInfo. In an example, UE requirements related to contents ofMasterinformationBlock-MBMS may not apply other than those specifiedelsewhere e.g. within procedures using concerned system information,and/or within corresponding field descriptions.

In an example, upon receiving a SystemInformationBlockType1 orSystemInformationBlockType1-BR either via broadcast and/or via dedicatedsignalling, a UE may: 1> if a cellAccessRelatedInfoList contains anentry with a PLMN-Identity of a selected PLMN: 2> in a remainder ofprocedures use plmn-IdentityList, trackingAreaCode, and/or cellIdentityfor a cell as received in a corresponding cellAccessRelatedInfoListcontaining a selected PLMN; 1> if in RRC_IDLE/RRC_INACTIVE or inRRC_CONNECTED while T311 is running; and/or 1> if a UE is a category 0UE; and/or 1> if category0Allowed is not included inSystemInformationBlockType1: 2> consider a cell as barred; 1> if inRRC_CONNECTED while T311 is not running, and/or a UE supports multi-bandcells as defined by bit 31 in featureGroupIndicators: 2> disregard afreqBandIndicator and/or multiBandInfoList, if received, while inRRC_CONNECTED; 2> forward a cellIdentity to upper layers; 2> forward atrackingAreaCode to upper layers; 1> else: 2> if a frequency bandindicated in a freqBandIndicator is part of frequency bands supported bya UE and it is not a downlink band; and/or 2> if a UE supportsmultiBandInfoList, and/or if one or more of frequency bands indicated ina multiBandInfoList are part of frequency bands supported by a UE andthey are not downlink bands: 3> forward a cellIdentity to upper layers;3> forward a trackingAreaCode to upper layers; 3> forward anims-EmergencySupport to upper layers, if present; 3> forwardeCallOverIMS-Support to upper layers, if present; 3> if, for a frequencyband selected by a UE (from freqBandIndicator or multiBandInfoList), afreqBandInfo and/or a multiBandInfoList-v10j0 is present and a UEcapable of multiNS-Pmax supports at least one additionalSpectrumEmissionin a NS-PmaxList within a freqBandInfo or multiBandInfoList-v10j0: 4>apply a first listed additionalSpectrumEmission which it may supportamong values included in NS-PmaxList within freqBandInfo ormultiBandInfolist-v10j0; 4> if an additionalPmax is present in a sameentry of a selected additionalSpectrumEmission within NS-PmaxList: 5>apply an additionalPmax; 4> else: 5> apply a p-Max; 3> else: 4> apply aadditionalSpectrumEmission in SystemInformationBlockType2 and/or ap-Max; 2> else: 3> consider a cell as barred; and/or 3> perform barringas if intraFreqReselection is set to notAllowed, and/or as if acsg-Indication is set to FALSE.

In an example, upon receiving a SystemInformationBlockType1-NB, a UEmay: 1> if a frequency band indicated in a freqBandIndicator is part offrequency bands supported by a UE; and/or 1> if one or more of frequencybands indicated in a multiBandInfoList are part of frequency bandssupported by a UE: 2> forward a cellIdentity to upper layers; 2> forwarda trackingAreaCode to upper layers; 2> if attachWithoutPDN-Connectivityis received for a selected PLMN: 3> forward anattachWithoutPDN-Connectivity to upper layers; 2> else 3> indicate toupper layers that attachWithoutPDN-Connectivity is not present; 2> if,for a frequency band selected by a UE (from freqBandIndicator ormultiBandInfoList), a freqBandInfo is present and a UE capable ofmultiNS-Pmax supports at least one additionalSpectrumEmission in aNS-PmaxList within a freqBandInfo: 3> apply a first listedadditionalSpectrumEmission which it may support among values included inNS-PmaxList within freqBandInfo; 3> if an additionalPmax is present in asame entry of a selected additionalSpectrumEmission within NS-PmaxList:4> apply an additionalPmax; 3> else: 4> apply a p-Max; 2> else: 3> applyan additionalSpectrumEmission in SystemInformationBlockType2-NB and ap-Max; 1> else: 2> consider a cell as barred; and/or 2> perform barringas if intraFreqReselection is set to notAllowed. In an example, UErequirements related to contents of SystemInformationBlockType1-MBMS maynot apply other than those specified elsewhere e.g. within proceduresusing concerned system information, and/or within corresponding fielddescriptions.

In an example, upon reception of SystemInformation messages, UErequirements related to contents of SystemInformation messages may notapply other than those specified elsewhere e.g. within procedures usingconcerned system information, and/or within corresponding fielddescriptions.

In an example, upon receiving SystemInformationBlockType2, a UE may: 1>apply a configuration included in a radioResourceConfigCommon; 1> ifupper layers indicate that a (UE specific) paging cycle is configured:2> apply a shortest of a (UE specific) paging cycle and adefaultPagingCycle included in a radioResourceConfigCommon; 1> if ambsfn-SubframeConfigList is included: 2> consider that DL assignmentsmay occur in a MBSFN subframes indicated in a mbsfn-SubframeConfigList;1> apply a specified PCCH configuration; 1> not apply atimeAlignmentTimerCommon; 1> if in RRC_CONNECTED and UE is configuredwith RLF timers and constants values received withinrlf-TimersAndConstants: 2> not update its values of timers and constantsin ue-TimersAndConstants except for a value of timer T300; 1> if inRRC_CONNECTED while T311 is not running; and/or a UE supports multi-bandcells as defined by bit 31 in featureGroupIndicators or multipleNS-Pmax:2> disregard an additionalSpectrumEmission and/or ul-CarrierFreq, ifreceived, while in RRC_CONNECTED; 1> if attachWithoutPDN-Connectivity isreceived for a selected PLMN: 2> forward attachWithoutPDN-Connectivityto upper layers; 1> else: 2> indicate to upper layers that attachWithoutPDN-Connectivity is not present; 1> if cp-CIoT-EPS-Optimisationis received for a selected PLMN: 2> forward cp-CIoT-EPS-Optimisation toupper layers; 1> else: 2> indicate to upper layers thatcp-CIoT-EPS-Optimisation is not present; 1> if up-CIoT-EPS-Optimisationis received for a selected PLMN: 2> forward up-CIoT-EPS-Optimisation toupper layers; 1> else: 2> indicate to upper layers thatup-CIoT-EPS-Optimisation is not present; 1> to upper layers eitherforward upperLayerIndication, if present for a selected PLMN, orotherwise indicate absence of this field; Upon receivingSystemInformationBlockType2-NB, a UE may: 1> apply a configurationincluded in a radioResourceConfigCommon; 1> apply a defaultPagingCycleincluded in a radioResourceConfigCommon; 1> ifSystemInformationBlockType22-NB is scheduled: 2> read and act oninformation sent in SystemInformationBlockType22-NB; 1> apply aspecified PCCH configuration. 1> if in RRC_CONNECTED and UE isconfigured with RLF timers and constants values received withinrlf-TimersAndConstants: 2> not update its values of timers and constantsin ue-TimersAndConstants except for a value of timer T300;

In an example, upon receiving SystemInformationBlockType3, a UE may: 1>if in RRC_IDLE/RRC_INACTIVE, a redistributionServingInfo is included anda UE is redistribution capable: 2> perform E-UTRAN inter-frequencyredistribution procedure; 1> if in RRC_IDLE/RRC_INACTIVE, or inRRC_CONNECTED while T311 is running: 2> if, for a frequency bandselected by a UE to represent serving cell's carrier frequency, afreqBandInfo or a multiBandInfoList-v10j0 is present inSystemInformationBlockType3 and/or a UE capable of multiNS-Pmax supportsat least one additionalSpectrumEmission in a NS-PmaxList within afreqBandInfo or multiBandInfoList-v10j0: 3> apply a first listedadditionalSpectrumEmission which it may support among values included inNS-PmaxList within freqBandInfo or multiBandInfoList-v10j0; 3> if anadditionalPmax is present in a same entry of a selectedadditionalSpectrumEmission within NS-PmaxList: 4> apply anadditionalPmax; 3> else: 4> apply a p-Max; 2> else: 3> apply a p-Max;

In an example, upon receiving SystemInformationBlockType3-NB, a UE may:1> if in RRC_IDLE, or in RRC_CONNECTED while T311 is running: 2> if, fora frequency band selected by a UE to represent a serving cell's carrierfrequency, a freqBandInfo or a multiBandInfoList is present inSystemInformationBlockType3-NB and/or a UE capable of multiNS-Pmaxsupports at least one additionalSpectrumEmission in a NS-PmaxList withina freqBandInfo or a multiBandInfoList: 3> apply a first listedadditionalSpectrumEmission which it may support among values included inNS-PmaxList within freqBandInfo or multiBandInfoList; 3> if anadditionalPmax is present in a same entry of a selectedadditionalSpectrumEmission within NS-PmaxList: 4> apply anadditionalPmax; 3> else: 4> apply a p-Max; 2> else: 3> apply a p-Max.

In an example, upon reception of SystemInformationBlockType4, UErequirements related to contents of this SystemInformationBlock(SystemInformationBlockType4 or SystemInformationBlockType4-NB) may notapply other than those specified elsewhere e.g. within procedures usingconcerned system information, and/or within corresponding fielddescriptions.

In an example, upon receiving SystemInformationBlockType5, a UE may: 1>if in RRC_IDLE/RRC_INACTIVE, a redistributionInterFreqInfo is includedand a UE is redistribution capable: 2> perform E-UTRAN inter-frequencyredistribution procedure; 1> if in RRC_IDLE/RRC_INACTIVE, or inRRC_CONNECTED while T311 is running: 2> if a frequency band selected bya UE to represent a non-serving E UTRA carrier frequency is not adownlink band: 3> if, for a selected frequency band, a freqBandInfo or amultiBandInfoList-v10j0 is present and/or a UE capable of multiNS-Pmaxsupports at least one additionalSpectrumEmission in a NS-PmaxList withinfreqBandInfo or multiBandInfoList-v10j0: 4> apply a first listedadditionalSpectrumEmission which it may support among values included inNS-PmaxList within freqBandInfo or multiBandInfoList-v10j0; 4> if anadditionalPmax is present in a same entry of a selectedadditionalSpectrumEmission within NS-PmaxList: 5> apply anadditionalPmax; 4> else: 5> apply a p-Max; 3> else: 4> apply a p-Max;

In an example, upon receiving SystemInformationBlockType5-NB, a UE may:1> if in RRC_IDLE/RRC_INACTIVE, or in RRC_CONNECTED while T311 isrunning: 2> if, for a frequency band selected by a UE (frommultiBandInfoList) to represent a non-serving NB-IoT carrier frequency,a freqBandInfo is present and/or a UE capable of multiNS-Pmax supportsat least one additionalSpectrumEmission in a NS-PmaxList within afreqBandInfo: 3> apply a first listed additionalSpectrumEmission whichit may support among values included in NS-PmaxList within freqBandInfo;3> if an additionalPmax is present in a same entry of a selectedadditionalSpectrumEmission within NS-PmaxList: 4> apply anadditionalPmax; 3> else: 4> apply a p-Max; 2> else: 3> apply a p-Max;

In an example, upon reception of SystemInformationBlockType6, UErequirements related to contents of this SystemInformationBlock may notapply other than those specified elsewhere e.g. within procedures usingconcerned system information, and/or within corresponding fielddescriptions.

In an example, UE requirements related to contents of thisSystemInformationBlock may not apply other than those specifiedelsewhere e.g. within procedures using concerned system information,and/or within corresponding field descriptions.

In an example, upon receiving SystemInformationBlockType8, a UE may: 1>if sib8-PerPLMN-List is included and a UE is capable of network sharingfor CDMA2000: 2> apply CDMA2000 parameters below corresponding to anRPLMN; 1> if a systemTimeInfo is included: 2> forward a systemTimeInfoto CDMA2000 upper layers; 1> if a UE is in RRC_IDLE and ifsearchWindowSize is included: 2> forward a searchWindowSize to CDMA2000upper layers; 1> if parametersHRPD is included: 2> forward apreRegistrationInfoHRPD to CDMA2000 upper layers if a UE has notreceived a preRegistrationInfoHRPD within anRRCConnectionReconfiguration message after entering this cell; 2> if acellReselectionParametersHRPD is included: 3> forward a neighCellList toa CDMA2000 upper layers; 1> if a parameters1×RTT is included: 2> if acsfb-RegistrationParam1×RTT is included: 3> forward acsfb-RegistrationParam1×RTT to CDMA2000 upper layers which may use thisinformation to determine if a CS registration/re-registration towardsCDMA2000 1×RTT in a EUTRA cell is required; 2> else: 3> indicate toCDMA2000 upper layers that CSFB Registration to CDMA2000 1×RTT may notbe allowed; 2> if a longCodeState1×RTT is included: 3> forward alongCodeState1×RTT to CDMA2000 upper layers; 2> if acellReselectionParameters1×RTT is included: 3> forward a neighCellListto CDMA2000 upper layers; 2> if csfb-SupportForDualRxUEs is included: 3>forward csfb-SupportForDualRxUEs to CDMA2000 upper layers; 2> else: 3>forward csfb-SupportForDualRxUEs, with its value set to FALSE, toCDMA2000 upper layers; 2> if ac-BarringConfig1×RTT is included: 3>forward ac-BarringConfig1×RTT to CDMA2000 upper layers; 2> if acsfb-DualRxTxSupport is included: 3> forward csfb-DualRxTxSupport toCDMA2000 upper layers; 2> else: 3> forward csfb-DualRxTxSupport, withits value set to FALSE, to CDMA2000 upper layers.

In an example, upon receiving SystemInformationBlockType9, a UE may: 1>if hnb-Name is included, forward a hnb-Name to upper layers. In anexample, upon receiving SystemInformationBlockType10, a UE may: 1>forward a received warningType, messageldentifier and serialNumber toupper layers. In an example, upon receivingSystemInformationBlockType11, a UE may: 1> if there is no current valuefor messageldentifier and serialNumber for SystemInformationBlockType11;and/or 1> if either a received value of messageldentifier or ofserialNumber or of both are different from current values ofmessageldentifier and serialNumber for SystemInformationBlockType11: 2>use received values of messageldentifier and serialNumber forSystemInformationBlockType11 as current values of messageldentifier andserialNumber for SystemInformationBlockType11; 2> discard previouslybuffered warningMessageSegment; 2> if segments of a warning message havebeen received: 3> assemble a warning message from a receivedwarningMessageSegment; 3> forward a received warning message,messageldentifier, serialNumber and dataCodingScheme to upper layers; 3>stop reception of SystemInformationBlockType11; 3> discard currentvalues of messageldentifier and serialNumber forSystemInformationBlockType11; 2> else: 3> store a receivedwarningMessageSegment; 3> continue reception ofSystemInformationBlockType11; 1> else if segments of a warning messagehave been received: 2> assemble a warning message from a receivedwarningMessageSegment; 2> forward a received complete warning message,messageldentifier, serialNumber and/or dataCodingScheme to upper layers;2> stop reception of SystemInformationBlockType11; 2> discard currentvalues of messageIdentifier and/or serialNumber forSystemInformationBlockType11; 1> else: 2> store a receivedwarningMessageSegment; 2> continue reception ofSystemInformationBlockType11; a UE may discard storedwarningMessageSegment and/or a current value of messageIdentifier and/orserialNumber for SystemInformationBlockType1l if a complete warningmessage has not been assembled within a period of 3 hours.

In an example, upon receiving SystemInformationBlockType12, a UE may: 1>if a SystemInformationBlockType12 contains a complete warning message:2> forward a received warning message, messageIdentifier, serialNumberand dataCodingScheme to upper layers; 2> continue reception ofSystemInformationBlockType12; 1> else: 2> if received values ofmessageIdentifier and serialNumber are a same (value is a same) as apair for which a warning message may be currently being assembled: 3>store a received warningMessageSegment; 3> if segments of a warningmessage have been received: 4> assemble a warning message from areceived warningMessageSegment; 4> forward a received warning message,messageIdentifier, serialNumber and/or dataCodingScheme to upper layers;4> stop assembling a warning message for this messageIdentifier and/orserialNumber and/or delete stored information held for it; 3> continuereception of SystemInformationBlockType12; 2> else if received values ofmessageIdentifier and/or serialNumber may not be the same as at leastone of pairs for which a warning message may be currently beingassembled: 3> start assembling a warning message for thismessageIdentifier and/or serialNumber pair; 3> store a receivedwarningMessageSegment; 3> continue reception ofSystemInformationBlockType12; a UE may discard warningMessageSegmentand/or associated values of messageIdentifier and/or serialNumber forSystemInformationBlockType12 if a complete warning message has not beenassembled within a period of 3 hours. The number of warning messagesthat a UE may re-assemble simultaneously may be a function of UEimplementation.

In an example, upon reception of SystemInformationBlockType13, UErequirements related to contents of this SystemInformationBlock may notapply other than those specified elsewhere e.g. within procedures usingconcerned system information, and/or within corresponding fielddescriptions.

In an example, upon reception of SystemInformationBlockType14, UErequirements related to contents of this SystemInformationBlock(SystemInformationBlockType14 or SystemInformationBlockType14-NB) maynot apply other than those specified elsewhere e.g. within proceduresusing concerned system information, and/or within corresponding fielddescriptions.

In an example, upon reception of SystemInformationBlockType15, UErequirements related to contents of this SystemInformationBlock(SystemInformationBlockType15 or SystemInformationBlockType15-NB) maynot apply other than those specified elsewhere e.g. within proceduresusing concerned system information, and/or within corresponding fielddescriptions.

In an example, upon reception of SystemInformationBlockType16, UErequirements related to contents of this SystemInformationBlock(SystemInformationBlockType16 or SystemInformationBlockType16-NB) maynot apply other than those specified elsewhere e.g. within proceduresusing concerned system information, and/or within corresponding fielddescriptions.

In an example, upon receiving SystemInformationBlockType17, a UE may: 1>if wlan-OffloadConfigCommon corresponding to a RPLMN is included: 2> ifa UE is not configured with rclwi-Configuration with command set tosteerToWLAN: 3> apply a wlan-Id-List corresponding to a RPLMN; 2> if notconfigured with a wlan-OffloadConfigDedicated: 3> apply awlan-OffloadConfigCommon corresponding to a RPLMN;

In an example, upon receiving SystemInformationBlockType18, a UE may: 1>if SystemInformationBlockType18 message includes a commConfig: 2> ifconfigured to receive sidelink communication: 3> from a next SC period,as defined by sc-Period, use a resource pool indicated by commRxPool forsidelink communication monitoring; 2> if configured to transmit sidelinkcommunication: 3> from a next SC period, as defined by sc-Period, use aresource pool indicated by commTxPoolNormalCommon,commTxPoolNormalCommonExt or by commTxPoolExceptional for sidelinkcommunication transmission.

In an example, upon receiving SystemInformationBlockType19, a UE may: 1>if SystemInformationBlockType19 message includes a discConfig ordiscConfigPS: 2> from a next discovery period, as defined by discPeriod,use resources indicated by discRxPool, discRxResourcesInterFreq ordiscRxPoolPS for sidelink discovery monitoring; 2> ifSystemInformationBlockType19 message includes a discTxPoolCommon ordiscTxPoolPS-Common; and a UE is in RRC_IDLE/RRC_INACTIVE: 3> from anext discovery period, as defined by discPeriod, use resources indicatedby discTxPoolCommon or discTxPoolPS-Common for sidelink discoveryannouncement; 2> if a SystemInformationBlockType19 message includes adiscTxPowerinfo: 3> use a power information included in discTxPowerinfofor sidelink discovery transmission on a serving frequency; 1> ifSystemInformationBlockType19 message includes a discConfigRelay: 2> if aSystemInformationBlockType19 message includes a txPowerInfo: 3> usepower information included in txPowerInfo for sidelink discoverytransmission on a corresponding non-serving frequency.

In an example, upon reception of SystemInformationBlockType20, UErequirements related to contents of this SystemInformationBlock(SystemInformationBlockType20 or SystemInformationBlockType20-NB) maynot apply other than those specified elsewhere e.g. within proceduresusing concerned system information, and/or within corresponding fielddescriptions.

In an example, upon receiving SystemInformationBlockType21, a UE may: 1>if SystemInformationBlockType21 message includes s1-V2X-ConfigCommon: 2>if configured to receive V2X sidelink communication: 3> use a resourcepool indicated by v2x-CommRxPool in s1-V2X-ConfigCommon for V2X sidelinkcommunication monitoring; 2> if configured to transmit V2X sidelinkcommunication: 3> use a resource pool indicated byv2x-CommTxPoolNormalCommon, p2x-CommTxPoolNormalCommon,v2x-CommTxPoolNormal, p2x-CommTxPoolNormal or byv2x-CommTxPoolExceptional for V2X sidelink communication transmission;3> perform CBR measurement on a transmission resource pool(s) indicatedby v2x-CommTxPoolNormalCommon, v2x-CommTxPoolNormal andv2x-CommTxPoolExceptional for V2X sidelink communication transmission.

In an example, upon reception of SystemInformationBlockType22-NB, UErequirements related to contents of this SystemInformationBlock may notapply other than those specified elsewhere e.g. within procedures usingconcerned system information, and/or within corresponding fielddescriptions.

In an example, when acquiring an SI message, a UE may: 1> determine astart of a SI-window for a concerned SI message as follows: 2> for aconcerned SI message, determine a number n which corresponds to an orderof entry in a list of SI messages configured by schedulingInfoList inSystemInformationBlockType1; 2> determine a integer value x=(n−1)*w,where w may be a si-WindowLength; 2> a SI-window may start at a subframe# a, where a=x mod 10, in a radio frame for which SFN mod T=FLOOR(x/10),where T may be a si-Periodicity of a concerned SI message; (E-UTRAN(e.g. NR, base station) may configure an SI-window of 1 ms if SIs arescheduled before subframe #5 in radio frames for which SFN mod 2=0) 1>receive DL-SCH using a SI-RNTI from a start of a SI-window and/orcontinue until an end of a SI-window whose absolute length in time maybe given by si-WindowLength, and/or until a SI message was received,excluding following subframes: 2> subframe #5 in radio frames for whichSFN mod 2=0; 2> MBSFN subframes; 2> uplink subframes in TDD; 1> if a SImessage was not received by an end of a SI-window, repeat reception at anext SI-window occasion for a concerned SI message.

In an example, when acquiring an SI message, a BL UE or UE in CE orNB-IoT UE may: 1> determine a start of a SI-window for a concerned SImessage as follows: 2> for a concerned SI message, determine the numbern which may correspond to an order of entry in a list of SI messagesconfigured by schedulingInfoList in SystemInformationBlockType1-BR (orSystemInformationBlockType1-NB in NB-IoT); 2> determine an integer valuex=(n−1)*w, where w may be a si-WindowLength-BR (or si-WindowLength inNB-IoT); 2> if a UE is a NB-IoT UE: 3> a SI-window starts at a subframe#0 in a radio frame for which (H-SFN*1024+SFN) mod T=FLOOR(x/10)+Offset,where T may be a si-Periodicity of a concerned SI message and, Offsetmay be an offset of a start of a SI-Window (si-RadioFrameOffset); 2>else: 3> a SI-window starts at a subframe #0 in a radio frame for whichSFN mod T=FLOOR(x/10), where T may be a si-Periodicity of a concerned SImessage; 1> if a UE is a NB-IoT UE: 2> receive and accumulate SI messagetransmissions on DL-SCH from a start of a SI-window and/or continueuntil an end of a SI-window whose absolute length in time may be givenby si-WindowLength, starting from radio frames as provided insi-RepetitionPattern and/or in subframes as provided in downlinkBitmap,or until successful decoding of an accumulated SI message transmissionsexcluding subframes used for transmission of NPSS, NSSS,MasterInformationBlock-NB and/or SystemInformationBlockType1-NB. Ifthere are not enough subframes for one SI message transmission in radioframes as provided in si-RepetitionPattern, a UE may continue to receivea SI message transmission in radio frames following a radio frameindicated in si-RepetitionPattern; 1> else: 2> receive and/or accumulateSI message transmissions on DL-SCH on narrowband provided bysi-Narrowband, from a start of a SI-window and/or continue until an endof a SI-window whose absolute length in time may be given bysi-WindowLength-BR, in radio frames as provided in si-RepetitionPatternand subframes as provided in fdd-DownlinkOrTddSubframeBitmapBR inbandwidthReducedAccessRelatedInfo, or until successful decoding of anaccumulated SI message transmissions; 1> if a SI message was notpossible to decode from accumulated SI message transmissions by an endof a SI-window, continue reception and/or accumulation of SI messagetransmissions on DL-SCH in a next SI-window occasion for a concerned SImessage.

In an example, when acquiring an SI message from MBMS-dedicated cell, aUE may: 1> determine a start of a SI-window for a concerned SI messageas follows: 2> for a concerned SI message, determine a number n whichmay correspond to an order of entry in a list of SI messages configuredby schedulingInfoList in SystemInformationBlockType1-MBMS; 2> determinean integer value x=(n−1)*w, where w is a si-WindowLength; 2> a SI-windowmay start at a subframe # a, where a=x mod 10, in a radio frame forwhich SFN mod T=FLOOR(x/10), where T may be a si-Periodicity of aconcerned SI message; 1> receive DL-SCH using SI-RNTI with value from astart of a SI-window and/or continue until an end of a SI-window whoseabsolute length in time may be given by si-WindowLength, or until a SImessage was received, excluding following subframes: 2> MBSFN subframes;1> if a SI message was not received by an end of a SI-window, repeatreception at a next SI-window occasion for a concerned SI message.

In existing wireless technologies as shown in FIG. 21, a base stationmay be shared by multiple network operators (e.g. multiple PLMNs). Whena base station is shared by multiple operators, protocol layers of thebase station (e.g. Physical, MAC, RLC, PDCP, RRC, SDAP) are shared bymultiple operators sharing the base station. In example FIG. 21, a gNBis shared by PLMN1 and PLMN2. The gNB communicates with AMF in 5G corenetwork of PLMN1 and AMF in 5G core of PLMN2. The gNB uses the radioprotocols layers for transmission of packets and control signaling ofboth PLMN1 and PLMN2.

For example, when a base station (e.g. gNB, eNB, BS) is utilized bymultiple network operators (e.g. multiple PLMNs), radio resource controlparameters of serving cells and/or wireless devices (e.g. UEs) may becommonly configured for the multiple operators. In an example, when abase station is utilized by multiple operators, the multiple operatorsmay configure common cell radio resource control parameters for the basestation. In existing technologies, when a base station is shared bymultiple operators, PHY/MAC/RLC/PDCP/RRC protocol layers are shared bymultiple operators. In existing network sharing technologies, commonconfiguration parameters and decision-making policies of serving cellsfor multiple operators may increase inefficient parameter settings andinappropriate decisions when serving wireless devices of differentoperators, which may have different network control policies.Implementation of existing parameter configuration mechanism of a basestation shared by multiple operators may not be efficient. The existingnetwork sharing technologies (e.g. base station sharing) may decreaseresource utilization and mobility performance of wireless devicesassociated with different operators. The existing network sharingtechnologies may increase call dropping rate and packet transmissiondelay when multiple operators share a base station. There is a need fordevelopment of enhanced base station sharing architecture and processesto enhance network performance when radio access network is shared.

Example embodiments provide enhanced network architecture for networksharing by implementing an enhanced base station sharing architectureand call/signaling processes. In an example embodiment, a base stationcentral unit (e.g. comprising RRC, PDCP, and/or SDAP layers) may be anon-shared node controlled by a network operator, and a base stationdistributed unit (e.g. comprising PHY, MAC, and/or RLC layers) may be ashared node shared by multiple network operators. Example embodimentsimplement decision making processes of a base station when multiplenetwork operators share a base station distributed unit whileimplementing their own non-shared base station central units. Exampleembodiment introduces a new network architecture comprising a sharedbase station distributed unit communicating with one or more non-sharedbase station central unit. This new architecture introduces newchallenges requiring implementation of enhanced call/signalingprocesses. The new network architecture and enhanced call/signalingprocesses improve communication reliability and configurationflexibility of the wireless network. Example embodiments enable multipleoperators to apply separate parameters configured based on theirseparate policies, by supporting different base station central unitsdetermining their configuration parameters separately for a shared basestation distributed unit. Example embodiments may reduce connectionfailure rate and/or radio quality degradation issues by introducing ashared base station distributed unit and separate non-shared basestation central units for multiple operators. Example embodiments mayimprove communication reliability by supporting base station distributedunit sharing for multiple base station central units of multipleoperators.

Example embodiments provide enhanced network architecture for networksharing, for example, base station sharing architecture and processes.In an example embodiment, a base station central unit comprising RRC,PDCP, and/or SDAP may be shared by a first set of one or more networkoperators, and a base station distributed unit may be a shared nodeshared by a second set of one or more network operators different fromthe first set of network operators. Implementation of such a complexnetwork architecture requires implementation of an enhancedcall/signaling flow. Example embodiment implement enhancedcall/signaling processes to enable this now network architecture.

A radio access network may be shared (e.g. utilized, used) by multipleoperators (e.g. multiple PLMNs, multiple service operators, and/or thelike). In an example, when a functional split of a gNB (e.g. basestation, eNB, RNC, and/or the like) onto multiple units (e.g. at leastone base station central unit (e.g. gNB-CU) and/or at least one basestation distributed unit (e.g. gNB-DU)) is configured, one of splitunits (e.g. at least one of gNB-CUs and/or gNB-DUs) may be shared bymultiple operators. In an example, when a gNB-DU is connected tomultiple gNB-CUs (e.g. base station central unit; a first gNB-CU and asecond gNB-CU), the gNB-DU may select a gNB-CU for a wireless deviceaccessing the gNB-DU and/or may select a gNB-CU based on load status ofgNB-CUs. In existing wireless technologies, a wireless device maytransmit an RRC message. A gNB-DU receiving an RRC message may forwardthe RRC message to a gNB-CU that may be inappropriate to the wirelessdevice (e.g. gNB-CU that may not support the wireless device).Implementation of existing RRC message forwarding mechanisms of a gNB-DUmay not be efficient. The existing technology may increase connectionlatency and packet transmission delay of wireless devices, and/or maydecrease access reliability and mobility performance of wirelessdevices. The existing technology may increase call dropping rate and/orpacket transmission delay when multiple gNB-CUs (e.g. multiple gNB-CUsoperated by a different operator each) are connected to a gNB-DU (e.g.shared gNB-DU).

Example embodiments enhance network node selection mechanism of a gNB-DUwhen multiple gNB-CUs are connected to a gNB-DU (e.g. when multiplegNB-CUs share a gNB-DU, when multiple operators share a base stationand/or serving cells, when multiple operators share a gNB-DU, and/or thelike). Example embodiments enhance a gNB-DU to support multiple gNB-CUs(e.g. multiple service operators, multiple operators, multiple PLMNs) byproviding gNB-CU selection mechanism of a gNB-DU for a wireless device.Example embodiments enhance a wireless device to provide gNB-CUinformation (e.g. gNB-CU identifier, gNB-identifier, gNB-CU address, gNBaddress, tracking area identifier, registration area identifier, and/orthe like) via an uplink message (e.g. RRC message) for gNB-CU selectionof a gNB-DU. Example embodiments enhance a wireless device to provideservice operator information (e.g. PLMN identifier, operator identifier,service operator identifier, cell identifier for a service operator,and/or the like) via an uplink message (e.g. RRC message) for gNB-CUselection of a gNB-DU. Example embodiments enhance a wireless device toprovide a cell identifier for a service operator (e.g. when multiplecell identifiers are configured for a cell shared by multiple serviceoperators) via an uplink message (e.g. RRC message) for core-node (e.g.AMF) selection of a gNB and/or for gNB-CU selection of a gNB-DU.

Example embodiments may decrease connection latency and packettransmission delay of wireless devices, and/or may increase accessreliability and mobility performance of wireless devices by introducinggNB-CU (or core node, AMF) selection mechanism of a gNB-DU (or basestation, gNB) for a wireless device. Example embodiments may improveaccess latency and communication reliability by supporting gNB-CUselection mechanism of a gNB-DU for a wireless device when a gNB-DUconnected to multiple gNB-CUs (e.g. of multiple service operators).Example embodiments may improve access latency and communicationreliability by supporting core node (AMF) selection mechanism of a basestation (gNB) for a wireless device when a gNB connected to multipleAMFs (e.g. of multiple service operators).

In an example embodiment, a gNB may be interpreted as an eNB, an RNC, ahome eNB, a home gNB, and/or any type of base stations or access points.In an example embodiment, a gNB-CU may be interpreted as a centralizedbase station (e.g. eNB-CU, RNC, access point central unit, and/or thelike). In an example embodiment, a gNB-DU may be interpreted as adistributed base station (e.g. eNB-DU, RRH, transmission and receptionpoint (TRP), access point distributed unit, and/or the like).

In an example, as shown in example figures: FIG. 16, FIG. 17, FIG. 18,FIG. 19, FIG. 20, FIG. 21, FIG. 22, and/or FIG. 23, one or more basestation central units (e.g. gNB-CUs, central units, CUs, and/or thelike) may be connected to one or more base station distributed units(e.g. gNB-DU, distributed unit, DU, and/or the like) via one or moreinterfaces (e.g. F1 interface). In an example, a base station maycomprise one or more base station central units and one or more basestation distributed units. In an example, a first base station centralunit (e.g. first gNB-CU, first central unit, first CU, first accesspoint CU, and/or the like) may be connected to a base stationdistributed unit (e.g. gNB-DU, distributed unit, DU, access point DU,and/or the like) via at least one first F1 interface (e.g. F1 user plane(F1-U), F1 control plane (F1-C)), and a second base station central unit(e.g. second gNB-CU, second central unit, second CU, second access pointCU, and/or the like) may be connected to the base station distributedunit (e.g. which is connected to the first base station control unit)via at least one second F1 interface. In an example, a base station(e.g. a gNB) may comprise the first gNB-CU, the second gNB-CU, and/orthe gNB-DU. In an example, a first base station may comprise the firstgNB-CU and/or the gNB-DU. In an example, a second base station maycomprise the second gNB-CU and/or the gNB-DU.

In an example, the first gNB-CU and/or the second gNB-CU may compriseupper layer control plane functions (e.g. RRC and/or the like) and/orupper layer user plane functions (e.g. SDAP, PDCP, and/or the like). ThegNB-DU may comprise lower layer functions (e.g. RLC, MAC, PHY, and/orthe like). In an example, the first gNB-CU and/or the second gNB-CU maycomprise at least RRC sublayer function. In an example, the gNB-DU maycomprise at least wireless transmitter and/or receiver for communicationwith wireless devices. In an example, the first gNB-CU and/or the secondgNB-CU may comprise upper layer functions (e.g., at least one of RRC,PDCP, SDAP, RLC, MAC, etc.). In an example, the gNB-DU may compriselower layer functions (e.g., at least one of PHY, MAC, etc.).

In an example, the first gNB-CU and/or the second gNB-CU maytransmit/receive PDCP packets (e.g. PDCP PDUs and/or PDCP SDUs) to/fromthe gNB-DU via an F1 interface (e.g. the at least one first F1 interfaceand/or the at least one second F1 interface). The gNB-DU may forward(transmit)/receive the PDCP packets to/from a wireless device via airinterface (e.g. Uu interface, radio). The gNB-DU may forward packets(e.g. PDCP packets, RLC packets, MAC packets) from a wireless device toa gNB-CU (e.g. the first gNB-CU or the second gNB-CU) and/or may forwardpackets (e.g. PDCP packets, RLC packets, MAC packets) from a gNB-CU(e.g. the first gNB-CU or the second gNB-CU) to a wireless device. In anexample, PDCP packets may be generated and transmitted by a wirelessdevice and/or may be generated and transmitted by a gNB-CU (e.g. thefirst gNB-CU and/or the second gNB-CU).

In an example, the first gNB-CU and/or the second gNB-CU may comprise abase station central unit control plane (e.g. gNB-CU-CP) and/or a basestation central unit user plane (e.g. gNB-CU-UP). In an example, agNB-CU-CP may comprise at least an RRC sublayer function. A gNB-CU-UPmay comprise an SDAP sublayer function, PDCP sublayer function, and/orthe like. A gNB-CU-CP and a gNB-CU-UP may be connected to each other viaan interface (e.g. E1 interface, E1-U, E1-C, and/or the like). In anexample, a gNB-CU-CP (e.g. a first gNB-CU-CP of the first gNB-CU and/ora second gNB-CU-CP of the second gNB-CU) may be connected with thegNB-DU via a F1 control plane interface (F1-CP) (e.g. a first F1-CP ofthe at least one first F1 interface and/or a second F1-CP of the atleast one second F1 interface). In an example, a gNB-CU-UP (e.g. a firstgNB-CU-UP of the first gNB-CU and/or a second gNB-CU-UP of the secondgNB-CU) may be connected with the gNB-DU via a F1 user plane interface(F1-UP) (e.g. a first F1-UP of the at least one first F1 interfaceand/or a second F1-UP of the at least one second F1 interface).

In an example, the gNB-DU may establish interface connections (e.g. F1connection, F1 control plane connection, F1 user plane connection) witha plurality of gNB-CUs. The plurality of gNB-CUs may comprise the firstgNB-CU and the second gNB-CU. In an example, the first gNB-CU maysupport (e.g. serve, be for, belong to, provide, and/or the like) afirst public land mobile network (PLMN). In an example, the secondgNB-CU may support (e.g. serve, be for, belong to, provide, and/or thelike) a second PLMN. In an example embodiment, supporting a PLMN (e.g.first PLMN, second PLMN) may be interpreted as being allowed/configuredto employ a corresponding network node (e.g. first gNB-CU, secondgNB-CU), corresponding resources, and/or a corresponding cell for thePLMN. That a network node supports a PLMN may be interpreted asresources of the network node is allowed to be used to operate the PLMNand/or serve wireless devices of the PLMN. That a network node supportsa PLMN may be interpreted as the PLMN comprises the network node.

A PLMN may be a combination of wireless communication services offeredby at least one operator in at least one country. A PLMN may compriseone or more cellular technologies such as GSM/2G, UMTS/3G, LTE/4G, 5G,and/or etc. offered by at least one operator within at least onecountry. A PLMN may be referred to as a cellular network.

In an example, as shown in FIG. 41, the gNB-DU may be shared by thefirst PLMN and the second PLMN. The first gNB-CU and/or the secondgNB-CU may be a non-shared gNB-CU. The first gNB-CU may be non-sharedwith the second PLMN. The second gNB-CU may be non-shared with the firstPLMN. Sharing a network node (e.g., gNB, gNB-CU, gNB-DU, etc.) withPLMNs may interpreted as sharing/using resources of the network nodewith the PLMNs.

In an example, the first gNB-CU may be shared by the first PLMN and atleast one third PLMN. In an example, the second gNB-CU may be shared bythe second PLMN and at least one fourth PLMN. In an example, the gNB-DUmay be shared by multiple PLMNs (e.g., multiple operators) comprising atleast one of the first PLMN, the second PLMN, the at least one thirdPLMN, and/or the at least one fourth PLMN.

In an example, as shown in example figures: FIG. 24, FIG. 25, FIG. 26,FIG. 27, FIG. 28, FIG. 29, FIG. 30, and/or FIG. 31, the first gNB-CU maytransmit (or send) a first connection message to the gNB-DU. The firstconnection message may comprise an F1 setup response message in responseto an F1 setup request message, which is transmitted by the gNB-DU tothe first gNB-CU. The F1 setup request message and the F1 setup responsemessage may be messages for an F1 setup procedure to establish an F1interface (e.g. the at least one first F1 interface) between the firstgNB-CU and the gNB-DU. In an example, the first connection message maycomprise a gNB-CU configuration update message for configuration updates(e.g. configurations of a gNB-CU and/or a gNB-DU) by a gNB-CU (e.g. thefirst gNB-CU). In response to receiving the gNB-CU configuration updatemessage, the gNB-DU may transmit, to the first gNB-CU, a gNB-CUconfiguration update acknowledge message (or a gNB-CU configurationupdate failure message), which may indicate that one or moreconfigurations of the gNB-CU configuration update message (e.g. thefirst connection message) are applied (accepted) or failed (rejected) atthe gNB-DU. The gNB-CU configuration update message and the gNB-CUconfiguration update acknowledge message (and/or the gNB-CUconfiguration update failure message) may be messages for a gNB-CUconfiguration update procedure. In an example, the first connectionmessage may comprise a gNB-DU configuration update acknowledge message(or a gNB-DU configuration update failure message) in response to agNB-DU configuration update message, which may be transmitted by thegNB-DU to the first gNB-CU. The gNB-DU configuration updated message andthe gNB-DU configuration update acknowledge message (and/or the gNB-DUconfiguration update failure message) may be messages for a gNB-DUconfiguration update procedure to update configurations (e.g.configurations of a gNB-CU and/or a gNB-DU) by a gNB-DU.

In an example, as shown in example figure, FIG. 32, FIG. 34, and/or FIG.35, the first connection message may comprise a first PLMN identifier ofa first PLMN supported (e.g. served) by the first gNB-CU. In an exampleembodiment, supporting a PLMN (e.g. first PLMN) may be interpreted asbeing allowed/configured to employ a corresponding network node (e.g.first gNB-CU), corresponding resources, and/or a corresponding cell forthe PLMN. In an example, the first PLMN may comprise the first gNB-CU.In an example, the first PLMN identifier may identify (or indicate) aPLMN (e.g. the first PLMN) of an operator (e.g. first service operator),an operator (e.g. first service operator), and/or a network served by anoperator (e.g. first service operator). An operator may be interpretedas a service operator/provider and/or a network operator/provider. In anexample, the first connection message may further comprise at least oneof a message type of the first connection message, a transactionidentifier (e.g. transaction ID) of a corresponding procedure (e.g. F1setup procedure, gNB-CU configuration update procedure, gNB-DUconfiguration update procedure, and/or the like), a gNB-CU identifier ofthe first gNB-CU, a gNB-CU name of the first gNB-CU, one or more firstcell identifiers (e.g. cell global identifier (NR CGI), physical cellidentifier (NR PCI)) of one or more first cells to be activated, one ormore second cell identifiers (e.g. cell global identifier (NR CGI),physical cell identifier (NR PCI)) of one or more second cells to bedeactivated, and/or the like. In an example, the first connectionmessage may further comprise one or more serving cell identifiers of oneor more serving cells associated with the first PLMN (e.g. one or morecells supporting the first PLMN, and/or one or more cells employed forthe first PLMN). In an example, the one or more serving cells may becells of the gNB-DU.

In an example, as shown in example figure FIG. 33, a first procedureinitiation message (e.g. the first connection message may be a responsemessage for the first procedure initiation message), e.g. the F1 setuprequest message and/or the gNB-DU configuration update message, maycomprise at least one of a message type of the first procedureinitiation message, a transaction identifier (e.g. transaction ID) of acorresponding procedure (e.g. F1 setup procedure, gNB-DU configurationupdate procedure, and/or the like), a gNB-DU identifier of the gNB-DU, agNB-DU name of the gNB-DU, served cell configuration parameters of oneor more served cells (e.g. to add/modify/delete/activate) of the gNB-DU,and/or the like. In an example, the served cell configuration parametersmay comprise at least one of served cell information of a served cell,gNB-DU system information of a served cell, and/or the like. The servedcell information may comprise at least one of a cell identifier (e.g. NRCGI, NR PCI, old NR CGI, old NR PCI), a tracking area code, a trackingarea identifier, one or more PLMN identifiers of one or more PLMNssupported by a served cell, FDD configuration parameters (e.g. uplinkfrequency band (UL ARFCN), downlink frequency band (DL ARFCN), ULtransmission bandwidth, DL transmission bandwidth, and/or the like), TDDconfiguration parameters (e.g. frequency band (ARFCN), transmissionbandwidth, and/or the like), LAA configuration parameters (e.g. subframetype3 configuration parameters), supplementary uplink (SUL) information,measurement timing configuration parameters, and/or the like. In anexample the gNB-DU system information may comprise at least one of amaster information block (MIB) message of a served cell, systeminformation block type 1 (SIB1) message of a served cell, and/or thelike.

In an example, as shown in example figure FIG. 36, a first procedureresponse message (e.g. a response message for the first connectionmessage), e.g. the gNB-CU configuration update acknowledge messageand/or the gNB-CU configuration update failure message, may comprise atleast one of a message type of the first procedure response message, atransaction identifier (e.g. transaction ID) of a correspondingprocedure (e.g. gNB-CU configuration update procedure, and/or the like),a gNB-DU identifier of the gNB-DU, a gNB-DU name of the gNB-DU, one ormore cell identifiers (e.g. NR CGI, NR PCI) of one or more cellssucceeded/failed to activate or modified/added/deleted, a cause ofsuccess/failure to activate or modification/addition/deletion, and/orthe like.

In an example, based on the first connection message, the gNB-DU mayconfigure one or more system parameters comprising at least one of F1interface configuration parameters (e.g. one or more tunnel identifierconfigurations of one or more tunnels to the first gNB-CU), cellconfiguration parameters of one or more serving cells associated withthe first gNB-CU (e.g. one or more serving cells employed for the firstgNB-CU and/or the first PLMN), resource configuration parameters (e.g.radio resource configuration parameters), hardware configurationparameters (e.g. CPU, RAM, bus resources for the first gNB-CU and/or thefirst PLMN), one or more configuration parameters for one or morewireless devices, and/or the like.

In an example, the second gNB-CU may transmit(send) a second connectionmessage to the gNB-DU. The second connection message may comprise an F1setup response message in response to an F1 setup request message, whichis transmitted by the gNB-DU to the second gNB-CU. The F1 setup requestmessage and the F1 setup response message may be messages for an F1setup procedure to establish an F1 interface (e.g. the at least onesecond F1 interface) between the second gNB-CU and the gNB-DU. In anexample, the second connection message may comprise a gNB-CUconfiguration update message for configuration updates (e.g.configurations of a gNB-CU and/or a gNB-DU) by a gNB-CU (e.g. the secondgNB-CU). In response to receiving the gNB-CU configuration updatemessage, the gNB-DU may transmit, to the second gNB-CU, a gNB-CUconfiguration update acknowledge message (or a gNB-CU configurationupdate failure message), which may indicate that one or moreconfigurations of the gNB-CU configuration update message (e.g. thesecond connection message) are applied (accepted) or failed (rejected)at the gNB-DU. The gNB-CU configuration update message and the gNB-CUconfiguration update acknowledge message (and/or the gNB-CUconfiguration update failure message) may be messages for a gNB-CUconfiguration update procedure. In an example, the second connectionmessage may comprise a gNB-DU configuration update acknowledge message(or a gNB-DU configuration update failure message) in response to agNB-DU configuration update message, which may be transmitted by thegNB-DU to the second gNB-CU. The gNB-DU configuration updated messageand the gNB-DU configuration update acknowledge message (and/or thegNB-DU configuration update failure message) may be messages for agNB-DU configuration update procedure to update configurations (e.g.configurations of a gNB-CU and/or a gNB-DU) by a gNB-DU.

In an example, the second connection message may comprise a second PLMNidentifier of a second PLMN supported (e.g. served) by the secondgNB-CU. In an example embodiment, supporting a PLMN (e.g. second PLMN)may be interpreted as being allowed/configured to employ a correspondingnetwork node (e.g. second gNB-CU), corresponding resources, and/or acorresponding cell for the PLMN. In an example, the second PLMN maycomprise the second gNB-CU. In an example, the second PLMN identifiermay identify (or indicate) a PLMN (e.g. the second PLMN) of an operator(e.g. second service operator), an operator (e.g. second serviceoperator), and/or a network served by an operator (e.g. second serviceoperator). In an example, the second connection message may furthercomprise at least one of a message type of the second connectionmessage, a transaction identifier (e.g. transaction ID) of acorresponding procedure (e.g. F1 setup procedure, gNB-CU configurationupdate procedure, gNB-DU configuration update procedure, and/or thelike), a gNB-CU identifier of the second gNB-CU, a gNB-CU name of thesecond gNB-CU, one or more third cell identifiers (e.g. cell globalidentifier (NR CGI), physical cell identifier (NR PCI)) of one or morethird cells to be activated, one or more fourth cell identifiers (e.g.cell global identifier (NR CGI), physical cell identifier (NR PCI)) ofone or more fourth cells to be deactivated, and/or the like. In anexample, the second connection message may further comprise one or moreserving cell identifiers of one or more serving cells associated withthe second PLMN (e.g. one or more cells supporting the second PLMN,and/or one or more cells employed for the second PLMN). In an example,the one or more serving cells may be cells of the gNB-DU.

In an example, a second procedure initiation message (e.g. the secondconnection message may be a response message for the second procedureinitiation message), e.g. the F1 setup request message and/or the gNB-DUconfiguration update message, may comprise at least one of a messagetype of the second procedure initiation message, a transactionidentifier (e.g. transaction ID) of a corresponding procedure (e.g. F1setup procedure, gNB-DU configuration update procedure, and/or thelike), a gNB-DU identifier of the gNB-DU, a gNB-DU name of the gNB-DU,served cell configuration parameters of one or more served cells (e.g.to add/modify/delete/activate) of the gNB-DU, and/or the like. In anexample, the served cell configuration parameters may comprise at leastone of served cell information of a served cell, gNB-DU systeminformation of a served cell, and/or the like. The served cellinformation may comprise at least one of a cell identifier (e.g. NR CGI,NR PCI, old NR CGI, old NR PCI), a tracking area code, a tracking areaidentifier, one or more PLMN identifiers of one or more PLMNs supportedby a served cell, FDD configuration parameters (e.g. uplink frequencyband (UL ARFCN), downlink frequency band (DL ARFCN), UL transmissionbandwidth, DL transmission bandwidth, and/or the like), TDDconfiguration parameters (e.g. frequency band (ARFCN), transmissionbandwidth, and/or the like), LAA configuration parameters (e.g. subframetype3 configuration parameters), supplementary uplink (SUL) information,measurement timing configuration parameters, and/or the like. In anexample the gNB-DU system information may comprise at least one of amaster information block (MIB) message of a served cell, systeminformation block type 1 (SIB1) message of a served cell, and/or thelike.

In an example, a second procedure response message (a response messagefor the second connection message), e.g. the gNB-CU configurationacknowledge message and/or the gNB-CU configuration failure message, maycomprise at least one of a message type of the second procedure responsemessage, a transaction identifier (e.g. transaction ID) of acorresponding procedure (e.g. gNB-CU configuration update procedure,and/or the like), a gNB-DU identifier of the gNB-DU, a gNB-DU name ofthe gNB-DU, one or more cell identifiers (e.g. NR CGI, NR PCI) of one ormore cells succeeded/failed to activate or modified/added/deleted, acause of success/failure to activate or modification/addition/deletion,and/or the like.

In an example, based on the second connection message, the gNB-DU mayconfigure one or more system parameters comprising at least one of F1interface configuration parameters (e.g. one or more tunnel identifierconfigurations of one or more tunnels to the second gNB-CU), cellconfiguration parameters of one or more serving cells associated withthe second gNB-CU (e.g. one or more serving cells employed for thesecond gNB-CU and/or the second PLMN), resource configuration parameters(e.g. radio resource configuration parameters), hardware configurationparameters (e.g. CPU, RAM, bus resources for the second gNB-CU and/orthe second PLMN), and/or the like.

In an example, based on the first connection message and/or the secondconnection message, the gNB-DU may support (e.g. serve, be part of,provide resources for, and/or the like) the first PLMN and the secondPLMN via serving cell(s) of the gNB-DU. In an example, one or more firstcells of the serving cells of the gNB-DU may support the first PLMN(and/or the first gNB-CU), and/or one or more second cells of theserving cells of the gNB-DU may support the second PLMN (and/or thesecond gNB-CU). In an example, one or more third cells of the gNB-DU maysupport both the first PLMN and the second PLMN. In an example, inresponse to receiving the first connection message, the gNB-DU maytransmit, to the first gNB-CU, one or more first cell identifiers of theone or more first cells supporting the first PLMN and/or one or morethird cell identifiers of the one or more third cells supporting thefirst PLMN and the second PLMN. In an example, in response to receivingthe second connection message, the gNB-DU may transmit, to the secondgNB-CU, one or more second cell identifiers of the one or more secondcells supporting the second PLMN and/or one or more third cellidentifiers of the one or more third cells supporting the first PLMN andthe second PLMN.

In an example, a PLMN identifier (e.g. the first PLMN identifier and/orthe second PLMN identifier) may comprise at least one of an operatoridentifier of a service operator, a network identifier of a networkserved by a service operator, a service area identifier of a servicearea served by a service operator, an identifier (identity) identifyinga PLMN/operator/service operator/network/network area/group ofinfrastructures, and/or the like. In an example, a PLMN (e.g. the firstPLMN and/or the second PLMN) may be interpreted at least one of anoperator, a service operator, a network served by a service operator, anetwork area, a service area served by a service operator, a group ofinfrastructures, and/or the like.

In an example, in response to receiving the second connection message,the gNB-DU may transmit (send), to the first gNB-CU, the second PLMNidentifier of the second PLMN that the gNB-DU (and/or a serving cell ofthe gNB-DU) supports (or serves), and/or may transmits, to the firstgNB-CU, a second gNB-CU identifier (e.g. a second gNB-CU name, secondgNB-CU IP address, and/or the like) of the second gNB-CU (e.g. thesecond gNB-CU identifier may indicate that the gNB-DU (and/or a servingcell of the gNB-DU) serves for the second gNB-CU). In an example, inresponse to receiving the second connection message, the gNB-DU maytransmit (send), to the first gNB-CU, the one or more first cellidentifiers of the one or more first cells supporting the first PLMN,the one or more second cell identifiers of the one or more second cellssupporting the second PLMN, and/or one or more third cell identifiers ofthe one or more third cells supporting the first PLMN and the secondPLMN.

In an example, in response to receiving the second connection messageand/or based on the first connection message, the gNB-DU may transmit(send), to the second gNB-CU, the first PLMN identifier of the firstPLMN that the gNB-DU (and/or a serving cell of the gNB-DU) supports (orserves) and/or may transmits, to the second gNB-CU, a first gNB-CUidentifier (and/or a first gNB-CU name, first gNB-CU IP address, and/orthe like) of the first gNB-CU (e.g. the first gNB-CU identifier mayindicate that the gNB-DU (and/or a serving cell of the gNB-DU) servesfor the first gNB-CU). In an example, in response to receiving thesecond connection message, the gNB-DU may transmit (send), to the secondgNB-CU, the one or more first cell identifiers of the one or more firstcells supporting the first PLMN, the one or more second cell identifiersof the one or more second cells supporting the second PLMN, and/or oneor more third cell identifiers of the one or more third cells supportingthe first PLMN and the second PLMN.

In an example, based on the first connection message and/or the secondconnection message, the gNB-DU may transmit (e.g. broadcast) at leastone third message (e.g. one or more system information block, at leastone system information block) comprising at least one of the first PLMNidentifier and/or the second PLMN identifier. The at least one thirdmessage may be transmitted via air interface (e.g. via serving cells ofthe gNB-DU, and/or radio interface). In an example, the at least onethird message may be (and/or comprise) one or more system informationblocks (e.g. master information block, system information block type 1,system information block type 2, system information block type 3, and/orthe like). In an example, the at least one third message may be (and/orcomprise) one or more radio resource control (RRC) messages (e.g. RRCconnection setup message, RRC connection resume message, RRC connectionreconfiguration message, RRC connection reestablishment message, and/orthe like) for a wireless device. In an example, the at least one thirdmessage may be transmitted via serving cells of the gNB-DU. In anexample, the at least one third message may be transmitted via at leastone of the one or more first cells supporting the first PLMN, the one ormore second cells supporting the second PLMN, and/or the one or morethird cells supporting the first PLMN and the second PLMN.

In an example, one or more of the at least one third message transmittedvia the one or more third cells may comprise the first PLMN identifierand/or the second PLMN identifier (e.g. both the first PLMN identifierand the second PLMN identifier, or either the first PLMN identifier orthe second PLMN identifier) indicating that the one or more third cellssupport (e.g. serve, are part of, provide resources for, and/or thelike) the first PLMN (e.g. the first gNB-CU) and/or the second PLMN(e.g. the second gNB-CU).

In an example, first one of the at least one third message transmittedvia the one or more first cells may comprise the first PLMN identifierindicating that the one or more first cells support (e.g. serve, arepart of, provide resources for, and/or the like) the first PLMN (e.g.the first gNB-CU). In an example, second one of the at least one thirdmessage transmitted via the one or more second cells may comprise thesecond PLMN identifier indicating that the one or more second cellssupport (e.g. serve, are part of, provide resources for, and/or thelike) the second PLMN (e.g. the second gNB-CU).

In an example, separate messages (e.g. separate system informationblocks, RRC messages) for different PLMNs (and/or different gNB-CUs) maybe transmitted as the at least one third message. In an example, a firstseparate message of the at least one third message may comprise thefirst PLMN identifier and/or a first serving cell identifier of aserving cell via which the first separate message (and/or the secondseparate message) is transmitted. In an example, a second separatemessage of the at least one third message may comprise the second PLMNidentifier and/or a second serving cell identifier of the serving cellvia which the second separate message (and/or the first separatemessage) is transmitted.

In an example, different cell identifiers (e.g. a first cell identifierand a second cell identifier) for a serving cell (e.g. physically singlecell; e.g., having different global cell identifiers for multiple PLMNs)may be configured for different PLMNs (e.g. the first PLMN and thesecond PLMN) (e.g. when the serving cell is employed to support/servethe first PLMN and the second PLMN). In an example, the different cellidentifiers may comprise a global cell identifier (GCI) and/or a cellglobal identifier (CGI), and/or the like. In an example, different cellidentifiers (e.g. a third cell identifier and a fourth cell identifier)for a serving cell (e.g. physically single cell) may be configured fordifferent gNB-CUs and/or for different gNBs (e.g. the first gNB-CU andthe second gNB-CU; and/or the first gNB of the first gNB-CU and thesecond gNB of the second gNB-CU) (e.g. when the serving cell is employedby the first gNB-CU and the second gNB-CU). In an example, the at leastone third message may comprise at least one cell identifier (e.g.comprising the first cell identifier for the first PLMN and/or thesecond cell identifier for the second PLMN) of the serving cell viawhich the at least one third message is transmitted. In an example, theat least one third message may comprise at least one cell identifier(e.g. comprising the third cell identifier for the first gNB-CU/thefirst gNB and/or the fourth cell identifier for the second gNB-CU/thesecond gNB) of the serving cell via which the at least one third messageis transmitted. In an example, the at least one cell identifier maycomprise at least one of a cell identity, a cell ID, a physical cellidentifier, a global cell identifier, and/or the like.

In an example, the at least one third message may comprise at least onetracking area code (TAC) of (and/or associated with) a serving cell viawhich the at least one third message may be transmitted. In an example,the at least one TAC may be configured for different PLMNs (e.g. a firstTAC of the at least one TAC may be configured for the first PLMN; and/ora second TAC of the at least one TAC may be configured for the secondPLMN). In an example, the at least one TAC may be configured fordifferent gNB-CUs (e.g. a third TAC of the at least one TAC may beconfigured for the first gNB-CU; and/or a fourth TAC of the at least oneTAC may be configured for the second gNB-CU). In an example, the atleast one TAC may comprise at least one of the first TAC, the secondTAC, the third TAC, and/or the fourth TAC.

In an example, the at least one third message may comprise at least onetracking area identifier (TAI) of (and/or associated with) a servingcell via which the at least one third message may be transmitted. In anexample, the at least one TAI may be configured for different PLMNs(e.g. a first TAI of the at least one TAI may be configured for thefirst PLMN; and/or a second TAI of the at least one TAI may beconfigured for the second PLMN). In an example, the at least one TAI maybe configured for different gNB-CUs (e.g. a third TAI of the at leastone TAI may be configured for the first gNB-CU; and/or a fourth TAI ofthe at least one TAI may be configured for the second gNB-CU). In anexample, the at least one TAI may comprise at least one of the firstTAI, the second TAI, the third TAI, and/or the fourth TAI.

In an example, the at least one third message may comprise at least oneregistration area code (RAC) of (and/or associated with) a serving cellvia which the at least one third message may be transmitted. In anexample, the at least one RAC may be configured for different PLMNs(e.g. a first RAC of the at least one RAC may be configured for thefirst PLMN; and/or a second RAC of the at least one TAC may beconfigured for the second PLMN). In an example, the at least one RAC maybe configured for different gNB-CUs (e.g. a third RAC of the at leastone RAC may be configured for the first gNB-CU; and/or a fourth RAC ofthe at least one RAC may be configured for the second gNB-CU). In anexample, the at least one RAC may comprise at least one of the firstRAC, the second RAC, the third RAC, and/or the fourth RAC.

In an example, the at least one third message may comprise at least oneregistration area identifier (RAI) of (and/or associated with) a servingcell via which the at least one third message may be transmitted. In anexample, the at least one RAI may be configured for different PLMNs(e.g. a first RAI of the at least one RAI may be configured for thefirst PLMN; and/or a second RAI of the at least one RAI may beconfigured for the second PLMN). In an example, the at least one RAI maybe configured for different gNB-CUs (e.g. a third RAI of the at leastone RAI may be configured for the first gNB-CU; and/or a fourth RAI ofthe at least one RAI may be configured for the second gNB-CU). In anexample, the at least one RAI may comprise at least one of the firstRAI, the second RAI, the third RAI, and/or the fourth RAI.

In an example, the at least one third message may comprise a firstgNB-CU identifier of the first gNB-CU and/or a second gNB-CU identifierof the second gNB-CU. The first gNB-CU identifier may indicate that aserving cell via which the at least one third message is transmittedserves for the first gNB-CU. The second gNB-CU identifier may indicatethat a serving cell via which the at least one third message istransmitted serves for the second gNB-CU.

In an example, the at least one third message may comprise a first gNBidentifier (e.g. a first base station identifier) of a first gNB (e.g. afirst base station) comprising the first gNB-CU and the gNB-DU. In anexample, the at least one third message may comprise a second gNBidentifier (e.g. a second base station identifier) of a second gNB (e.g.a second base station) comprising the second gNB-CU and the gNB-DU. Inan example, the first gNB identifier (e.g. associated with the firstgNB-CU and/or the first PLMN) and the second gNB identifier (e.g.associated with the second gNB-CU and/or the second PLMN) may be for agNB (e.g. a base station; the first gNB and the second gNB are the samegNB) comprising the first gNB-CU, the second gNB-CU, and the gNB-DU. Thefirst gNB identifier may be for the first gNB-CU and/or the first PLMN.The second gNB identifier may be for the second gNB-CU and/or the secondPLMN. The first gNB identifier may indicate that a serving cell viawhich the at least one third message is transmitted serves for the firstgNB, the first gNB-CU, and/or the first PLMN. The second gNB identifiermay indicate that a serving cell via which the at least one thirdmessage is transmitted serves for the second gNB, the second gNB-CU,and/or the second PLMN.

In an example, the at least one third message may comprise at least oneRAN notification area (RNA) identifier (e.g. for a wireless device inRRC inactive state) of (and/or associated with) a serving cell via whichthe at least one third message may be transmitted. In an example, the atleast one RNA identifier may be configured for different PLMNs (e.g. afirst RNA identifier of the at least one RNA identifier may beconfigured for the first PLMN; and/or a second RNA identifier of the atleast one RNA identifier may be configured for the second PLMN). In anexample, the at least one RNA identifier may be configured for differentgNB-CUs (e.g. a third RNA identifier of the at least one RNA identifiermay be configured for the first gNB-CU; and/or a fourth RNA identifierof the at least one RNA identifier may be configured for the secondgNB-CU). In an example, the at least one RNA identifier may comprise atleast one of the first RNA identifier, the second RNA identifier, thethird RNA identifier, and/or the fourth RNA identifier.

In an example, the at least one third message may comprise at least oneRAN area identifier (e.g. for a wireless device in RRC inactive state)of (and/or associated with) a serving cell via which the at least onethird message may be transmitted. In an example, the at least one RANarea identifier may be configured for different PLMNs (e.g. a first RANarea identifier of the at least one RAN area identifier may beconfigured for the first PLMN; and/or a second RAN area identifier ofthe at least one RAN area identifier may be configured for the secondPLMN). In an example, the at least one RAN area identifier may beconfigured for different gNB-CUs (e.g. a third RAN area identifier ofthe at least one RAN area identifier may be configured for the firstgNB-CU; and/or a fourth RAN area identifier of the at least one RAN areaidentifier may be configured for the second gNB-CU). In an example, theat least one RAN area identifier may comprise at least one of the firstRAN area identifier, the second RAN area identifier, the third RAN areaidentifier, and/or the fourth RAN area identifier.

In an example, the at least one third message may comprise at least oneresume identifier (e.g. for a wireless device in RRC inactive state) for(and/or associated with) a serving cell via which the at least one thirdmessage may be transmitted. In an example, the at least one resumeidentifier may be configured for different PLMNs (e.g. a first resumeidentifier of the at least one resume identifier may be for the firstPLMN; and/or a second resume identifier of the at least one resumeidentifier may be for the second PLMN). In an example, the at least oneresume identifier may be configured for different gNB-CUs (e.g. a thirdresume identifier of the at least one resume identifier may be for thefirst gNB-CU; and/or a fourth resume identifier of the at least oneresume identifier may be for the second gNB-CU). In an example, the atleast one resume identifier may comprise at least one of the firstresume identifier, the second resume identifier, the third resumeidentifier, and/or the fourth resume identifier.

In an example, the at least one third message may comprise at least oneof a cell barred information element (IE), intra frequency IE, closedsubscriber group (CSG) indication, a CSG identifier (e.g. CSG identity),a cell selection IE comprising q-RxLevMin and/or q-RxLevMinOffset, ap-Max, frequency band information comprising additionalPmax value and/oradditionalSpectrumEmission value, scheduling information, TDDconfiguration information, a system information window length, a systeminformation value tag, and/or the like for a serving cell via which theat least one third message is transmitted.

In an example, the gNB-DU may configure the at least one third message,and/or may transmit (e.g. broadcast) the at least one third message viaair interface (e.g. via serving cells of the gNB-DU, and/or radiointerface).

In an example, the gNB-DU may configure the at least one third message,and/or may transmit the at least one third message to the first gNB-CUand/or the second gNB-CU via an F1 interface (e.g. the at least onefirst F1 interface and/or the at least one second F1 interface; e.g. viaa gNB-DU configuration update message, an F1 setup request message, agNB-CU configuration update acknowledge message, an UL RRC messagetransfer message, a system information transfer message, and/or thelike) (if the first gNB-CU is a master CU, the gNB-DU transmit the atleast one third message to the first gNB-CU). Based on the at least onethird message received from the gNB-DU, the first gNB-CU and/or thesecond gNB-CU may transmit, to the gNB-DU, the at least one thirdmessage via the F1 interface (e.g. the at least one first F1 interfaceand/or the at least one second F1 interface; e.g. via a gNB-CUconfiguration update message, an F1 setup response message, a gNB-DUconfiguration update acknowledge message, an DL RRC message transfermessage, a system information transfer message, and/or the like) (if thefirst gNB-CU is a master CU, the first gNB-CU transmit the at least onethird message to the gNB-DU). In an example, in response to receivingthe at least one third message from the first gNB-CU and/or the secondgNB-CU, the gNB-DU may transmit (and/or broadcast) the at least onethird message via air interface (e.g. via the serving cells of thegNB-DU, and/or radio interface).

In an example, the gNB-DU may configure one or more parameters of the atleast one third message, and/or may transmit the one or more parametersof the at least one third message to the first gNB-CU and/or the secondgNB-CU via an F1 interface (e.g. the at least one first F1 interfaceand/or the at least one second F1 interface; e.g. via a gNB-DUconfiguration update message, an F1 setup request message, a gNB-CUconfiguration update acknowledge message, an UL RRC message transfermessage, a system information transfer message, and/or the like) (if thefirst gNB-CU is a master CU, the gNB-DU transmit the one or moreparameters of the at least one third message to the first gNB-CU). Basedon the one or more parameters of the at least one third message, thefirst gNB-CU and/or the second gNB-CU may transmit, to the gNB-DU, theat least one third message via the F1 interface (e.g. the at least onefirst F1 interface and/or the at least one second F1 interface; e.g. viaa gNB-CU configuration update message, an F1 setup response message, agNB-DU configuration update acknowledge message, an DL RRC messagetransfer message, a system information transfer message, and/or thelike) (if the first gNB-CU is a master CU, the first gNB-CU transmit theat least one third message to the gNB-DU). In an example, in response toreceiving the at least one third message from the first gNB-CU and/orthe second gNB-CU, the gNB-DU may transmit (and/or broadcast) the atleast one third message via air interface (e.g. via the serving cells ofthe gNB-DU, and/or radio interface).

In an example, the gNB-DU may configure at least one system informationblock (e.g. the at least one third message, one or more elements of theat least one third message, system information block type 1, and/orother types of system information block: for example, SIB2, SIB3, etc.)for a serving cell of the gNB-DU based on the first connection messageand/or the second connection message. In an example, the at least onesystem information block may comprise at least one of the first PLMNidentifier, the second PLMN identifier, a first parameter indicatingthat the serving cell supports the first PLMN (e.g. first serviceoperator, first operator, first network, and/or the like), a secondparameter indicating that the serving cell supports the second PLMN(e.g. second service operator, second operator, second network, and/orthe like), a third parameter indicating that the serving cell isemployed by the first gNB-CU and/or the first gNB, a fourth parameterindicating that the serving cell is employed by the second gNB-CU and/orthe second gNB, and/or the like. The at least one system informationblock may further comprise at least one of a cell identifier of aserving cell via which the at least one system information block istransmitted, the first cell identifier of the serving cell for the firstPLMN, the second cell identifier of the serving cell for the secondPLMN, the third cell identifier of the serving cell for the firstgNB-CU/the first gNB, the fourth cell identifier of the serving cell forthe second gNB-CU/the second gNB, and/or the like. The first parametermay comprise at least one of the first TAC, the first TAI, the firstRAC, the first RAI, the first cell identifier, the first gNB-CUidentifier, the first gNB identifier, the first RNA identifier, thefirst RAN area identifier, the first resume identifier, and/or the like.The second parameter may comprise at least one of the second TAC, thesecond TAI, the second RAC, the second RAI, the second cell identifier,the second gNB-CU identifier, the second gNB identifier, the second RNAidentifier, the second RAN area identifier, the second resumeidentifier, and/or the like. The third parameter may comprise at leastone of the third TAC, the third TAI, the third RAC, the third RAI, thethird cell identifier, the first gNB-CU identifier, the first gNBidentifier, the third RNA identifier, the third RAN area identifier, thethird resume identifier, and/or the like. The fourth parameter maycomprise at least one of the fourth TAC, the fourth TAI, the fourth RAC,the fourth RAI, the fourth cell identifier, the second gNB-CUidentifier, the second gNB identifier, the fourth RNA identifier, thefourth RAN area identifier, the fourth resume identifier, and/or thelike.

In an example, based on the first PLMN identifier of the first PLMNand/or the second PLMN identifier of the second PLMN supported by aserving cell of the gNB-DU (e.g. received from the gNB-DU) and/or basedon the first parameter, the second parameter, the third parameter,and/or the fourth parameter, the first gNB-CU may configure at least onesystem information block (e.g. system information block type 1, and/orother types of system information block: for example, SIB2, SIB3, etc.)for the serving cell of the gNB-DU. In an example, the first gNB-CU mayreceive the first PLMN identifier and/or the second PLMN identifier fromthe gNB-DU and/or from the second gNB-CU. In an example, the firstgNB-CU may receive the first parameter, the second parameter, the thirdparameter, and/or the fourth parameter from the gNB-DU and/or from thesecond gNB-CU. In an example, the at least one system information blockmay comprise the first PLMN identifier, the second PLMN identifier, thefirst parameter indicating that the serving cell supports the first PLMN(e.g. first service operator, first operator, first network, and/or thelike), the second parameter indicating that the serving cell supportsthe second PLMN (e.g. second service operator, second operator, secondnetwork, and/or the like), the third parameter indicating that theserving cell is employed by the first gNB-CU and/or the first gNB, thefourth parameter indicating that the serving cell is employed by thesecond gNB-CU and/or the second gNB, and/or the like. The at least onesystem information block may further comprise at least one of a cellidentifier of a serving cell via which the at least one systeminformation block is transmitted, the first cell identifier of theserving cell for the first PLMN, the second cell identifier of theserving cell for the second PLMN, the third cell identifier of theserving cell for the first gNB-CU/the first gNB, the fourth cellidentifier of the serving cell for the second gNB-CU/the second gNB,and/or the like. The first parameter may comprise at least one of thefirst TAC, the first TAI, the first RAC, the first RAI, the first cellidentifier, the first gNB-CU identifier, the first gNB identifier, thefirst RNA identifier, the first RAN area identifier, the first resumeidentifier, and/or the like. The second parameter may comprise at leastone of the second TAC, the second TAI, the second RAC, the second RAI,the second cell identifier, the second gNB-CU identifier, the second gNBidentifier, the second RNA identifier, the second RAN area identifier,the second resume identifier, and/or the like. The third parameter maycomprise at least one of the third TAC, the third TAI, the third RAC,the third RAI, the third cell identifier, the first gNB-CU identifier,the first gNB identifier, the third RNA identifier, the third RAN areaidentifier, the third resume identifier, and/or the like. The fourthparameter may comprise at least one of the fourth TAC, the fourth TAI,the fourth RAC, the fourth RAI, the fourth cell identifier, the secondgNB-CU identifier, the second gNB identifier, the fourth RNA identifier,the fourth RAN area identifier, the fourth resume identifier, and/or thelike.

In an example, the gNB-DU may transmit/broadcast the at least one systeminformation block configured by the gNB-DU and/or received from thefirst gNB-CU and/or the second gNB-CU (e.g. configured by the firstgNB-CU and/or the second gNB-CU). The at least one system informationblock may be transmitted/broadcasted via radio interface to a pluralityof wireless devices.

In an example, as shown in example figures, FIG. 41 and/or FIG. 42,separate cells of the gNB-DU may be configured for different PLMNs. Inan example, one or more first serving cells of serving cells of thegNB-DU may support (e.g. serve, be part of, provide resources for,and/or the like) the first PLMN (and/or the first gNB-CU and/or thefirst gNB). At least one message (transmitted/broadcasted via the one ormore first cells by the gNB-DU to wireless devices) of the at least onethird message may comprise the first PLMN identifier, a first gNB-CUidentifier of the first gNB-CU, a first gNB identifier of a first gNBassociated with the first gNB-CU, one or more first serving cellidentifiers of the one or more first serving cells, and/or the like. Inan example, the one or more first serving cell identifiers may betransmitted from the gNB-DU to the first gNB-CU. In an example, one ormore second serving cells of serving cells of the gNB-DU may support(e.g. serve, be part of, provide resources for, and/or the like) thesecond PLMN (and/or the second gNB-CU and/or the second gNB). At leastone message (transmitted/broadcasted via the one or more second cells bythe gNB-DU to wireless devices) of the at least one third message maycomprise the second PLMN identifier, a second gNB-CU identifier of thesecond gNB-CU, a second gNB identifier of a second gNB associated withthe second gNB-CU, one or more second serving cell identifiers of theone or more second serving cells, and/or the like. In an example, theone or more second serving cell identifiers may be transmitted from thegNB-DU to the second gNB-CU.

In an example, as shown in example figures, FIG. 41 and/or FIG. 42,common cells of the gNB-DU may be configured for multiple PLMNs (e.g.the first PLMN and/or the second PLMN; the first gNB-CU and/or thesecond gNB-CU; and/or the first gNB and/or the second gNB). In anexample, one or more third serving cells of serving cells of the gNB-DUmay support (e.g. serve, be part of, provide resources for, and/or thelike) the first PLMN and the second PLMN (and/or the first gNB-CU andthe second gNB-CU). At least one message (transmitted/broadcasted viathe one or more third serving cells by the gNB-DU to wireless devices)of the at least one third message may comprise the first PLMN identifierand the second PLMN identifier, a first gNB-CU identifier of the firstgNB-CU and a second gNB-CU identifier of the second gNB-CU, a first gNBidentifier of the first gNB associated with the first gNB-CU and asecond gNB identifier of the second gNB associated with the secondgNB-CU, one or more third serving cell identifiers of the one or morethird serving cells, (e.g. if different (multiple) cell identifiers fora serving cell are configured for different PLMNs) one or more fourthserving cell identifiers (associated with the first PLMN, the firstgNB-CU, and/or the first gNB) of (or for) the one or more third servingcells, (e.g. if different (multiple) cell identifiers for a serving cellare configured for different PLMNs) one or more fifth serving cellidentifiers (associated with the second PLMN, the second gNB-CU, and/orthe second gNB) of (or for) the one or more third serving cells, and/orthe like. In an example, the one or more third serving cell identifiers,the one or more fourth serving cell identifiers, and/or the one or morefifth serving cell identifiers may be transmitted from the gNB-DU to thefirst gNB-CU. In an example, the one or more third serving cellidentifiers, the one or more fourth serving cell identifiers, and/or theone or more fifth serving cell identifiers may be transmitted from thegNB-DU to the second gNB-CU. In an example, the first gNB-CU mayconfigure the one or more fourth serving cell identifiers, and maytransmit to the gNB-DU. In an example, the second gNB-CU may configurethe one or more fifth serving cell identifiers, and may transmit to thegNB-DU.

In an example, as shown in example figure FIG. 37, at least one systeminformation block (e.g. SIB1, SIB2, SIB3, SIB4, SIB5, and/or the like)may comprise multiple configuration parameters or multiple configuredsystem information blocks for multiple PLMNs (and/or for multiplegNB-CUs). At least one of the first gNB-CU and/or the second gNB-CU mayreceive parameters of other gNB-CU (e.g. the second gNB-CU or the firstgNB-CU respectively) via the gNB-DU, and/or may configure the at leastone system information block. In an example, the base stationdistributed unit may receive, from the second base station central unit,one or more second configuration parameters associated with the secondbase station central unit and/or the second PLMN. The base stationdistributed unit may transmit, to the first base station central unit,the one or more second configuration parameters. The base stationdistributed unit may receive, from the first base station central unit,at least one system information block comprising at least one of: one ormore first configuration parameters (e.g. and/or a first systeminformation block) associated with the first base station central unitand/or the first PLMN; and/or the one or more second configurationparameters (e.g. and/or a second system information block) associatedwith the second base station central unit and/or the second PLMN. Thebase station distributed unit may transmit (forward/broadcast) the atleast one system information block. The base station distributed unitmay transmit, to the second base station central unit, the at least onesystem information block.

In an example, as shown in example figure FIG. 37, at least one systeminformation block (e.g. SIB1, SIB2, SIB3, SIB4, SIB5, and/or the like)may comprise multiple configuration parameters or multiple configuredsystem information blocks for multiple PLMNs (and/or for multiplegNB-CUs). At least one of the first gNB-CU and/or the second gNB-CU mayreceive parameters of other gNB-CU (e.g. the second gNB-CU or the firstgNB-CU respectively) via an interface between the first gNB-CU and thesecond gNB-CU, and/or may configure the at least one system informationblock. In an example, the base station distributed unit may receive,from the first base station central unit, at least one systeminformation block comprising at least one of: one or more firstconfiguration parameters (e.g. and/or a first system information block)associated with the first base station central unit and/or the firstPLMN; and/or one or more second configuration parameters (e.g. and/or asecond system information block) associated with the second base stationcentral unit and/or the second PLMN. The first base station central unitmay receive the one or more second configuration parameters from thesecond base station central unit (e.g. via an interface between thefirst gNB-CU and the second gNB-CU). The base station distributed unitmay transmit (forward/broadcast) the at least one system informationblock. In an example, the base station distributed unit may transmit, tothe second base station central unit, the at least one systeminformation block.

In an example, as shown in example figure FIG. 38, at least one systeminformation block (e.g. SIB1, SIB2, SIB3, SIB4, SIB5, and/or the like)may comprise multiple configuration parameters or multiple configuredsystem information blocks for multiple PLMNs (and/or for multiplegNB-CUs). The gNB-DU may receive, from the first gNB-CU and/or thesecond gNB-CU, parameters of the first gNB-CU (e.g. the first PLMN)and/or of second gNB-CU (e.g. the second PLMN), and/or may configure theat least one system information block. In an example, the base stationdistributed unit may receive, from the first base station central unit,one or more first configuration parameters associated with the firstbase station central unit and/or the first PLMN. The base stationdistributed unit may receive, from the second base station central unit,one or more second configuration parameters associated with the secondbase station central unit and/or the second PLMN. The base stationdistributed unit may determine at least one system information blockcomprising at least one of: the one or more first configurationparameters (e.g. and/or a first system information block) associatedwith the first gNB-CU and/or the first PLMN; and/or the one or moresecond configuration parameters (e.g. and/or a second system informationblock) associated with the second base station central unit and/or thesecond PLMN. (In an example, the base station distributed unit maytransmit, to the first base station central unit and/or the second basestation central unit, the at least one system information block. Thebase station distributed unit may receive, from the first base stationcentral unit and/or the second base station central unit, the at leastone system information block.) In an example, the base stationdistributed unit may transmit (forward/broadcast) the at least onesystem information block.

In an example, as shown in example figure FIG. 38, at least one systeminformation block (e.g. SIB1, SIB2, SIB3, SIB4, SIB5, and/or the like)may comprise multiple configuration parameters or multiple configuredsystem information blocks for multiple PLMNs (and/or for multiplegNB-CUs). The gNB-DU may receive, from the first gNB-CU and/or thesecond gNB-CU, parameters of the first gNB-CU (e.g. the first PLMN)and/or the second gNB-CU (e.g. the second PLMN). In an example, one ofthe first gNB-CU and the second gNB-CU may receive parameters of othergNB-CU (e.g. the second gNB-CU or the first gNB-CU respectively) via aninterface between the first gNB-CU and the second gNB-CU, and/or maytransmit to the gNB-DU. The gNB-DU may configure the at least one systeminformation block based on the parameters. In an example, the basestation distributed unit may receive, from the first base stationcentral unit, at least one of: one or more first configurationparameters associated with the first base station central unit and/orthe first PLMN; and/or one or more second configuration parametersassociated with the second base station central unit and/or the secondPLMN. The first base station central unit may receive the one or moresecond configuration parameters from the second base station centralunit. The base station distributed unit may determine at least onesystem information block comprising the one or more first configurationparameters (e.g. and/or a first system information block) associatedwith the first base station central unit and/or the first PLMN and/orthe one or more second configuration parameters (e.g. and/or a secondsystem information block) associated with the second base stationcentral unit and/or the second PLMN. (In an example, the base stationdistributed unit may transmit, to the first base station central unitand/or the second base station central unit, the at least one systeminformation block. The base station distributed unit may receive, fromthe first base station central unit and/or the second base stationcentral unit, the at least one system information block.) In an example,the base station distributed unit may transmit (forward/broadcast) theat least one system information block.

In an example, as shown in example figure FIG. 39, at least one systeminformation block (e.g. SIB1, SIB2, SIB3, SIB4, SIB5, and/or the like)may comprise configuration parameters (e.g. (partially) common and/or(partially) separated) for multiple PLMNs (and/or for multiple gNB-CUs).At least one of the first gNB-CU and/or the second gNB-CU may receiveparameters of other gNB-CU (e.g. the second gNB-CU or the first gNB-CUrespectively) via the gNB-DU, and/or may configure the at least onesystem information block. In an example, the base station distributedunit may receive, from the second base station central unit, one or moresecond configuration parameters associated with the second base stationcentral unit and/or the second PLMN. The base station distributed unitmay transmit, to the first base station central unit, the one or moresecond configuration parameters. The base station distributed unit mayreceive, from the first base station central unit, at least one systeminformation block comprising one or more configuration parametersassociated with the first PLMN and/or the second PLMN (and/or associatedwith the first base station central unit and/or the second base stationcentral unit). The base station distributed unit may transmit(forward/broadcast) the at least one system information block. The basestation distributed unit may transmit, to the second base stationcentral unit, the at least one system information block.

In an example, as shown in example figure FIG. 39, at least one systeminformation block (e.g. SIB1, SIB2, SIB3, SIB4, SIBS, and/or the like)may comprise configuration parameters (e.g. (partially) common and/or(partially) separated) for multiple PLMNs (and/or for multiple gNB-CUs).At least one of the first gNB-CU and/or the second gNB-CU may receiveparameters of other gNB-CU (e.g. the second gNB-CU or the first gNB-CUrespectively) via an interface between the first gNB-CU and the secondgNB-CU, and/or may configure the at least one system information block.In an example, the base station distributed unit may receive, from thefirst base station central unit, at least one system information blockcomprising one or more configuration parameters associated with thefirst PLMN and/or the second PLMN (and/or associated with the first basestation central unit and/or the second base station central unit). Thebase station distributed unit may transmit (forward/broadcast) the atleast one system information block. The base station distributed unitmay transmit, to the second base station central unit, the at least onesystem information block.

In an example, as shown in example figure FIG. 40, at least one systeminformation block (e.g. SIB1, SIB2, SIB3, SIB4, SIB5, and/or the like)may comprise configuration parameters (e.g. (partially) common and/or(partially) separated) for multiple PLMNs (and/or for multiple gNB-CUs).The gNB-DU may receive, from the first gNB-CU and/or the second gNB-CU,parameters of the first gNB-CU (e.g. the first PLMN) and/or of secondgNB-CU (e.g. the second PLMN), and/or may configure the at least onesystem information block. In an example, the base station distributedunit may receive, from the first base station central unit, one or morefirst configuration parameters associated with the first base stationcentral unit and/or the first PLMN, and/or may receive, from the secondbase station central unit, one or more second configuration parametersassociated with the second base station central unit and/or the secondPLMN. In an example, the base station distributed unit may determine,based on the one or more first configuration parameters and/or the oneor more second configuration parameters, at least one system informationblock comprising one or more configuration parameters associated withthe first PLMN and/or the second PLMN (and/or associated with the firstbase station central unit and/or the second base station central unit).(In an example, the base station distributed unit may transmit, to thefirst base station central unit and/or the second base station centralunit, the at least one system information block. The base stationdistributed unit may receive, from the first base station central unitand/or the second base station central unit, the at least one systeminformation block.) In an example, the base station distributed unit maytransmit (forward/broadcast) the at least one system information block.

In an example, as shown in example figure FIG. 40, at least one systeminformation block (e.g. SIB1, SIB2, SIB3, SIB4, SIBS, and/or the like)may comprise configuration parameters (e.g. (partially) common and/or(partially) separated) for multiple PLMNs (and/or for multiple gNB-CUs).The gNB-DU may receive, from the first gNB-CU and/or the second gNB-CU,parameters of the first gNB-CU (e.g. the first PLMN) and/or the secondgNB-CU (e.g. the second PLMN). In an example, one of the first gNB-CUand the second gNB-CU may receive parameters of other gNB-CU (e.g. thesecond gNB-CU or the first gNB-CU respectively) via an interface betweenthe first gNB-CU and the second gNB-CU, and/or may transmit to thegNB-DU. The gNB-DU may configure the at least one system informationblock based on the parameters. In an example, the base stationdistributed unit may receive, from the first base station central unit,at least one of: one or more first configuration parameters associatedwith the first base station central unit and/or the first PLMN; and/orone or more second configuration parameters associated with the secondbase station central unit or the second PLMN. The first base stationcentral unit may receive the one or more second configuration parametersfrom the second base station central unit. The base station distributedunit may determine, based on the one or more first configurationparameters and/or the one or more second configuration parameters, atleast one system information block comprising one or more configurationparameters associated with the first PLMN and/or the second PLMN (orassociated with the first base station central unit and/or the secondbase station central unit). (In an example, the base station distributedunit may transmit, to the first base station central unit and/or thesecond base station central unit, the at least one system informationblock. The base station distributed unit may receive, from the firstbase station central unit and/or the second base station central unit,the at least one system information block.) In an example, the basestation distributed unit may transmit (forward/broadcast) the at leastone system information block.

In an example, a wireless device may select a serving cell of the gNB-DUbased on the at least one third message and/or the at least one systeminformation block. The wireless device may select/reselect the servingcell of the gNB-DU based on the first PLMN identifier and/or the secondPLMN identifier of the at least one third message. The wireless devicemay select/reselect the serving cell of the gNB-DU based on the firstcell identifier, the second cell identifier, the third cell identifier,and/or the fourth cell identifier for the serving cell of the at leastone third message. The wireless device may select/reselect the servingcell of the gNB-DU based on the first gNB-CU identifier and/or thesecond gNB-CU identifier of the at least one third message. The wirelessdevice may select/reselect the serving cell of the gNB-DU based on thefirst gNB identifier associated with the first gNB-CU and/or the secondgNB identifier associated with the second gNB-CU of the at least onethird message.

In an example, the wireless device may select/reselect the serving cellof the gNB-DU based on one or more elements of the first parameter, thesecond parameter, the third parameter, and/or the fourth parameter ofthe at least one third message. The first parameter may comprise atleast one of the first TAC, the first TAI, the first RAC, the first RAI,the first cell identifier, the first gNB-CU identifier, the first gNBidentifier, the first RNA identifier, the first RAN area identifier, thefirst resume identifier, and/or the like. The second parameter maycomprise at least one of the second TAC, the second TAI, the second RAC,the second RAI, the second cell identifier, the second gNB-CUidentifier, the second gNB identifier, the second RNA identifier, thesecond RAN area identifier, the second resume identifier, and/or thelike. The third parameter may comprise at least one of the third TAC,the third TAI, the third RAC, the third RAI, the third cell identifier,the first gNB-CU identifier, the first gNB identifier, the third RNAidentifier, the third RAN area identifier, the third resume identifier,and/or the like. The fourth parameter may comprise at least one of thefourth TAC, the fourth TAI, the fourth RAC, the fourth RAI, the fourthcell identifier, the second gNB-CU identifier, the second gNBidentifier, the fourth RNA identifier, the fourth RAN area identifier,the fourth resume identifier, and/or the like. In an example, thewireless device may be in an RRC idle state, an RRC inactive state,and/or an RRC connected state.

In an example, the wireless device may have a list of PLMN identifiersof PLMNs allowed (and/or able) to access (e.g. the list of PLMNidentifiers may comprise a PLMN identifier of an equivalent PLMN). Inresponse to at least one of the first PLMN and/or the second PLMN beingin the list of the PLMNs allowed to access (e.g. and/or the first PLMNand/or the second PLMN may comprise an equivalent PLMN), the wirelessdevice may select (and/or reselect) the serving cell of the gNB-DU. Inan example, the wireless device may have a list of cell identifiers ofcells allowed (and/or able) to access. In response to at least one ofthe first cell identifier, the second cell identifier, the third cellidentifier, and/or the fourth cell identifier being in the list of thecell identifiers of the cells allowed to access, the wireless device mayselect (and/or reselect) the serving cell of the gNB-DU. In an example,the wireless device may have a list of networks (e.g. TAC, TAI, RAC,RAI, gNB-CU, gNB, RNA, RAN area, and/or resume identifier) allowed(and/or able) to access. In response to at least one element of thefirst parameter, the second parameter, the third parameter, and/or thefourth parameter being in the list of the networks allowed to access,the wireless device may select (and/or reselect) the serving cell of thegNB-DU.

In an example, based on the selection of the serving cell of the gNB-DUby the wireless device, the wireless device may initiate one or morerandom access procedures to access to the serving cell of the gNB-DU.The wireless device may transmit one or more random access preambles viathe serving cell, and may receive at least one random access response(RAR) for the one or more random access preambles via the serving cellfrom the gNB-DU. In an example, the wireless device may determine thatone of the one or more random access procedures is on processing and/orsuccessful based on interactions (comprising at least one of the one ormore random access preambles and/or the at least one random accessresponse) with the gNB-DU.

In an example, based on the selection of the serving cell of the gNB-DUby the wireless device and/or based on the one or more random accessprocedures of the wireless device, the gNB-DU may receive, from thewireless device, a first message (e.g. RRC message, RRC connectionrequest message, RRC connection setup complete message, RRC connectionresume request message, RRC connection resume complete message, and/orthe like). In an example, in response to receiving the at least one RARfor the one or more random access preambles, the wireless device maytransmit the first message (e.g. RRC connection request message and/orRRC connection resume request message; e.g. message3). The first messagemay comprise at least one of the first PLMN identifier (e.g. indicatingthat the wireless device is accessible to the first PLMN) and/or thesecond PLMN identifier (e.g. indicating that the wireless device isaccessible to the second PLMN). In an example, the first PLMN identifiermay comprise a first indication/index (e.g., one or more first bits)indicating the first PLMN. In an example, the second PLMN identifier maycomprise a second indication/index (e.g., one or more second bits)indicating the second PLMN. In an example, the first message maycomprise at least one of the first cell identifier (e.g. indicating thatthe wireless device is accessible/tries to access to the first celland/or the first PLMN), the second cell identifier (e.g. indicating thatthe wireless device is accessible/tries to access to the second celland/or the second PLMN), the third cell identifier (e.g. indicating thatthe wireless device is accessible/tries to access to the third celland/or the first gNB-CU/the first gNB), and/or the fourth cellidentifier (e.g. indicating that the wireless device is accessible/triesto access to the fourth cell and/or the second gNB-CU/the second gNB).The wireless device may send the first message based on the at least onethird message and/or the at least one system information block. Thewireless device may determine the first PLMN and/or the second PLMNbased on the third message and/or the at least one system informationblock. Based on the determining, the wireless device may include/add thefirst PLMN identifier (e.g., or the first cell identifier) and/or thesecond PLMN identifier (e.g., or the second cell identifier) in thefirst message.

In an example, the first message may comprise at least one of one ormore of the first parameter, one or more of the second parameter, one ormore of the third parameter, and/or one or more of the fourth parameter.The one or more of the first parameter may indicate that the firstmessage is for connection to the first PLMN and/or a network (e.g.tracking area, registration area, RNA, RAN area, and/or the like)associated with the first PLMN. The one or more of the second parametermay indicate that the first message is for connection to the second PLMNand/or a network (e.g. tracking area, registration area, RNA, RAN area,and/or the like) associated with the second PLMN. The one or more of thethird parameter may indicate that the first message is for connection tothe first gNB-CU/the first gNB and/or a network (e.g. tracking area,registration area, RNA, RAN area, and/or the like) associated with thefirst gNB-CU/the first gNB. The one or more of the fourth parameter mayindicate that the first message is for connection to the secondgNB-CU/the second gNB and/or a network (e.g. tracking area, registrationarea, RNA, RAN area, and/or the like) associated with the secondgNB-CU/the second gNB.

In an example, if the wireless device selects the serving cell and thefirst PLMN to access, the first message may comprise at least one of thefirst PLMN identifier, the first cell identifier (and/or the third cellidentifier), the first gNB identifier, the first gNB-CU identifier, thefirst TAC, the first TAI, the first RAC, the first RAI, the first RNAidentifier, the first RAN area identifier, the first resume identifier,and/or the like.

In an example, if the wireless device selects the serving cell and thesecond PLMN to access, the first message may comprise at least one ofthe second PLMN identifier, the second cell identifier (and/or thefourth cell identifier), the second gNB identifier, the second gNB-CUidentifier, the second TAC, the second TAI, the second RAC, the secondRAI, the second RNA identifier, the second RAN area identifier, thesecond resume identifier, and/or the like.

In an example, if the wireless device selects the serving cell and thefirst gNB-CU and/or the first gNB to access, the first message maycomprise at least one of the first PLMN identifier, the third cellidentifier (and/or the first cell identifier), the first gNB identifier,the first gNB-CU identifier, the third TAC, the third TAI, the thirdRAC, the third RAI, the third RNA identifier, the third RAN areaidentifier, the third resume identifier, and/or the like.

In an example, if the wireless device selects the serving cell and thesecond gNB-CU and/or the second gNB to access, the first message maycomprise at least one of the second PLMN identifier, the fourth cellidentifier (and/or the second cell identifier), the second gNBidentifier, the second gNB-CU identifier, the fourth TAC, the fourthTAI, the fourth RAC, the fourth RAI, the fourth RNA identifier, thefourth RAN area identifier, the fourth resume identifier, and/or thelike.

In an example, at least one of the first PLMN identifier, the first cellidentifier, the first gNB identifier, at least one of the first gNB-CUidentifier, the first TAC, the first TAI, the first RAC, the first RAI,the first RNA identifier, the first RAN area identifier, the firstresume identifier, the second PLMN identifier, the second cellidentifier, the second gNB identifier, the second gNB-CU identifier, thesecond TAC, the second TAI, the second RAC, the second RAI, the secondRNA identifier, the second RAN area identifier, the second resumeidentifier, the third cell identifier, the third TAC, the third TAI, thethird RAC, the third RAI, the third RNA identifier, the third RAN areaidentifier, the third resume identifier, the fourth cell identifier, thefourth TAC, the fourth TAI, the fourth RAC, the fourth RAI, the fourthRNA identifier, the fourth RAN area identifier, and/or the fourth resumeidentifier may be transmitted from the wireless device to the gNB-DU(e.g. the base station) via MAC control element (e.g. MAC CE) and/orphysical layer control information (e.g. UCI) with the first message.

In an example, a selected PLMN identity (identifier) information elementof the first message may comprise the at least one of the first PLMNidentifier and/or the second PLMN identifier. In an example, if thewireless device is allowed (and/or accessible, able, authorized) toaccess to (and/or employ) the first PLMN, the first message may comprisethe first PLMN identifier. In an example, if the wireless device isallowed (and/or accessible, able, authorized) to access to (and/oremploy) the second PLMN, the first message may comprise the second PLMNidentifier (e.g. and/or the first cell identifier (and/or the third cellidentifier), the first gNB identifier, the first gNB-CU identifier, thefirst TAC, the first TAI, the first RAC, the first RAI, the first RNAidentifier, the first RAN area identifier, the first resume identifier,and/or the like). In an example, if the wireless device is allowed(and/or accessible, able, authorized) to access to (and/or employ) thefirst PLMN and the second PLMN, the first message may comprise the firstPLMN identifier and the second PLMN identifier (e.g. and/or the secondcell identifier (and/or the fourth cell identifier), the second gNBidentifier, the second gNB-CU identifier, the second TAC, the secondTAI, the second RAC, the second RAI, the second RNA identifier, thesecond RAN area identifier, the second resume identifier, and/or thelike). In an example, if the wireless device is allowed (and/oraccessible, able, authorized) to access to (and/or employ) the firstPLMN and the second PLMN, the first message may further comprise apriority information between the first PLMN and the second PLMN.

In an example, the first message may comprise an RRC message. In anexample, the first message may comprise at least one of a wirelessdevice identifier (e.g. TMSI, S-TMSI, IMSI, C-RNTI, RNTI, Resume ID,and/or the like) of the wireless device, a counter check responsemessage, a CSFB parameters request CDMA2000 message, an in-devicecoexistence (IDC) indication message, an inter frequency RSTDmeasurement indication message, an MBMS counting response message, anMBMS interest indication message, a measurement report message, aproximity indication message, a relay node reconfiguration completemessage, an RRC connection reconfiguration complete message, an RRCconnection reestablishment request message, an RRC connectionreestablishment complete message, an RRC connection request message, anRRC connection setup complete message, an RRC connection resume requestmessage, an RRC connection resume complete message, a secondary cellgroup (SCG) failure information (NR) message, a security mode completemessage, a sidelink UE information message, a UE assistance informationmessage, a UE capability information message, a UE information responsemessage, a UE handover preparation transfer message, an uplinkinformation transfer message (e.g. comprising at least one NAS message),an uplink information transfer MRDC message, a WLAN connection statusreport message, and/or an RRC message associated with the wirelessdevice.

In an example, the first message may comprise at least one of aregistered core network node information (e.g. a registered mobilitymanagement entity (MME), a registered access and mobility managementfunction (AMF), a registered session management function (SMF), aregistered serving gateway (SGW), a registered user plane function(UPF), a registered PDN gateway (PGW), and/or the like), a registered(e.g. preferred) base station information (e.g. registered base stationidentifier, a registered gNB, a registered gNB identifier, the first gNBidentifier, the second gNB identifier, a first eNB identifier, a secondeNB identifier, and/or the like), a registered (e.g. preferred) gNB-CUinformation (e.g. a gNB-CU identifier, the first gNB-CU identifier, thesecond gNB-CU identifier, and/or the like), a dedicated non-accessstratum information (e.g. information between a core network(MME/AMF/SMF) and the wireless device), a RAN notification areaidentifier, a RAN area information associated with the wireless device(e.g. in an RRC inactive state), a GUMMEI type (e.g. native, mapped), aradio link failure information available information, a relay nodesubframe configuration request, mobility status information (e.g. movingspeed of the wireless device, for example, high/medium/low/normal/staticspeed), a mobility history available information (e.g. list of cells atwhich the wireless device stayed), a logged measurement result availableinformation (e.g. associated with MBSFN), a wireless device identifier(e.g. S-TMSI, IMSI, TMSI, and/or the like) of the wireless device, aresume identifier (e.g. resume ID) of the wireless device (e.g. in anRRC inactive state), an information of attach-without-PDN-connectivity,an user plane cellular Internet-of-things (CIoT) optimizationinformation (e.g. indicating data transmission based on user plane CIoToptimization), an control plane cellular Internet-of-things (CIoT)optimization information (e.g. indicating data transmission based oncontrol plane CIoT optimization), a dcn identifier (e.g. dcn ID), aregistered MME (e.g. comprising a PLMN identity (the first PLMNidentifier and/or the second PLMN identifier), MMEGI, MMEC, and/or thelike), and/or the like.

In an example, in response to receiving the first message, the gNB-DUmay select a central unit (e.g. as a selected gNB-CU) (e.g. between thefirst gNB-CU and the second gNB-CU) based on the first message. In anexample, in response to receiving the first message, the gNB-DU mayselect a central unit (e.g. as a selected gNB-CU) at least between thefirst gNB-CU and the second gNB-CU based on the at least one of thefirst PLMN identifier and/or the second PLMN identifier of the firstmessage. In an example, if the first message comprises the first PLMNidentifier (e.g. indicates that the wireless device is allowed (and/oraccessible, able, authorized) to access to (and/or employ) the firstPLMN), the gNB-DU may select the first gNB-CU to forward the firstmessage and/or one or more elements of the first message. In an example,if the first message comprises the second PLMN identifier (e.g.indicates that the wireless device is allowed (and/or accessible, able,authorized) to access to (and/or employ) the second PLMN), the gNB-DUmay select the second gNB-CU to forward the first message and/or one ormore elements of the first message. In an example, if the first messagecomprises the first PLMN identifier and the second PLMN identifier (e.g.indicates that the wireless device is allowed (and/or accessible, able,authorized) to access to (and/or employ) the first PLMN and the secondPLMN), the gNB-DU may select one of the first gNB-CU or the secondgNB-CU to forward the first message and/or one or more elements of thefirst message (e.g. based on the priority information of the first PLMNand the second PLMN indicated in the first message).

In an example, in response to receiving the first message, the gNB-DUmay select a central unit (e.g. as a selected gNB-CU) at least betweenthe first gNB-CU and the second gNB-CU based on the at least one offirst PLMN related parameters and/or second PLMN related parameters ofthe first message. In an example, if the first message comprises atleast one of the first PLMN identifier, the first cell identifier(and/or the third cell identifier), the first gNB identifier, the firstgNB-CU identifier, the first TAC, the first TAI, the first RAC, thefirst RAI, the first RNA identifier, the first RAN area identifier, thefirst resume identifier, and/or the like (e.g. indicating that thewireless device is allowed (and/or accessible, able, authorized) toaccess to (and/or employ) the first PLMN and/or the serving cell), thegNB-DU may select the first gNB-CU to forward the first message and/orone or more elements of the first message. In an example, if the firstmessage comprises at least one of the second PLMN identifier, the secondcell identifier (and/or the fourth cell identifier), the second gNBidentifier, the second gNB-CU identifier, the second TAC, the secondTAI, the second RAC, the second RAI, the second RNA identifier, thesecond RAN area identifier, the second resume identifier, and/or thelike (e.g. indicating that the wireless device is allowed (and/oraccessible, able, authorized) to access to (and/or employ) the secondPLMN and/or the serving cell), the gNB-DU may select the second gNB-CUto forward the first message and/or one or more elements of the firstmessage.

In an example, in response to receiving the first message, the gNB-DUmay select a central unit (e.g. as a selected gNB-CU) at least betweenthe first gNB-CU and the second gNB-CU based on the at least one offirst gNB-CU related parameters (e.g. first gNB related parameters)and/or second gNB-CU related parameters (e.g. second gNB relatedparameters) of the first message. In an example, if the first messagecomprises at least one of the first PLMN identifier, the third cellidentifier (and/or the first cell identifier), the first gNB identifier,the first gNB-CU identifier, the third TAC, the third TAI, the thirdRAC, the third RAI, the third RNA identifier, the third RAN areaidentifier, the third resume identifier, and/or the like (e.g.indicating that the wireless device is allowed (and/or accessible, able,authorized) to access to (and/or employ) the first gNB-CU/the first gNBand/or the serving cell), the gNB-DU may select the first gNB-CU toforward the first message and/or one or more elements of the firstmessage. In an example, if the first message comprises at least one ofthe second PLMN identifier, the fourth cell identifier (and/or thesecond cell identifier), the second gNB identifier, the second gNB-CUidentifier, the fourth TAC, the fourth TAI, the fourth RAC, the fourthRAI, the fourth RNA identifier, the fourth RAN area identifier, thefourth resume identifier, and/or the like (e.g. indicating that thewireless device is allowed (and/or accessible, able, authorized) toaccess to (and/or employ) the second gNB-CU/the second gNB and/or theserving cell), the gNB-DU may select the second gNB-CU to forward thefirst message and/or one or more elements of the first message.

In an example, in response to receiving the first message, the gNB-DUmay select a central unit (e.g. as a selected gNB-CU) at least betweenthe first gNB-CU and the second gNB-CU based on the serving cell viawhich the wireless device transmits the first message to the gNB-DU. Inan example, if the gNB-DU receives the first message via the one or morefirst serving cells (e.g. supporting the first PLMN and/or the firstgNB-CU/the first gNB), the gNB-DU may select the first gNB-CU to forwardthe first message and/or one or more elements of the first message. Inan example, if the gNB-DU receives the first message via the one or moresecond serving cells (e.g. supporting the second PLMN and/or the secondgNB-CU/the second gNB), the gNB-DU may select the second gNB-CU toforward the first message and/or one or more elements of the firstmessage. In an example, if the gNB-DU receives the first message via theone or more third serving cells (e.g. supporting the first PLMN and thesecond PLMN; and/or supporting the first gNB-CU/the first gNB and thesecond gNB-CU/the second gNB), the gNB-DU may select the first gNB-CUand/or the second gNB-CU to forward the first message and/or one or moreelements of the first message (e.g. the gNB-DU may transmit/forward thefirst message to the first gNB-CU and/or the second gNB-CU (e.g. toeither the first gNB-CU or the second gNB-CU; or to both the firstgNB-CU and the second gNB-CU)).

In an example, the gNB-DU may select a central unit (gNB-CU) between thefirst gNB-CU and the second gNB-CU based on one or more elements of thefirst message (e.g. the registered core network node information, theregistered (preferred) base station information, the registered (e.g.preferred) gNB-CU information, the RAN notification area identifier, theRAN area information, and/or the like). In an example, if the one ormore elements of the first message are associated with the firstgNB-CU/the first gNB and/or the first PLMN, the gNB-DU may select thefirst gNB-CU to forward the first message and/or one or more elements ofthe first message. In an example, if the one or more elements of thefirst message are associated with the second gNB-CU/the second gNBand/or the second PLMN, the gNB-DU may select the second gNB-CU toforward the first message and/or one or more elements of the firstmessage. In an example, if a registered core network node of theregistered core network node information (e.g. MME, AMF, SMF, UPF, SGW,PGW, and/or the like) is connected to (e.g. serve, operate, control, hasan NG/S1 interface with, and/or the like) the first gNB-CU/the firstgNB, the gNB-DU may select the first gNB-CU to forward the first messageand/or one or more elements of the first message. In an example, if aregistered core network node of the registered core network nodeinformation (e.g. MME, AMF, SMF, UPF, SGW, PGW, and/or the like) isconnected to (e.g. serve, operate, control, has an NG/S1 interface with,and/or the like) the second gNB-CU/the second gNB, the gNB-DU may selectthe second gNB-CU to forward the first message and/or one or moreelements of the first message.

In an example, if a registered base station (e.g. gNB, eNB, RNC, and/orthe like) of the registered (preferred) base station informationcomprises (e.g. is associated with) the first gNB-CU identifier/thefirst gNB identifier, the gNB-DU may select the first gNB-CU to forwardthe first message and/or one or more elements of the first message. Inan example, if a registered base station (e.g. gNB, eNB, RNC, and/or thelike) of the registered (preferred) base station information comprises(e.g. is associated with) the second gNB-CU identifier/the second gNBidentifier, the gNB-DU may select the first gNB-CU (or the second gNB-CUcorrespondingly) to forward the first message and/or one or moreelements of the first message.

In an example, if a registered gNB-CU of the registered (e.g. preferred)gNB-CU information comprises the first gNB-CU, the gNB-DU may select thefirst gNB-CU to forward the first message and/or one or more elements ofthe first message. In an example, if a registered gNB-CU of theregistered (e.g. preferred) gNB-CU information comprises the secondgNB-CU, the gNB-DU may select the second gNB-CU to forward the firstmessage and/or one or more elements of the first message.

In an example, if a RAN notification area of the RAN notification areaidentifier and/or a RAN area of the RAN area information comprise(s) thefirst gNB-CU/the first gNB, the gNB-DU may select the first gNB-CU toforward the first message and/or one or more elements of the firstmessage. In an example, if a RAN notification area of the RANnotification area identifier and/or a RAN area of the RAN areainformation comprise(s) the second gNB-CU/the second gNB, the gNB-DU mayselect the second gNB-CU to forward the first message and/or one or moreelements of the first message.

In an example, based on the selection of a gNB-CU based on the firstmessage and/or one or more elements of the first message, the gNB-DU maytransmit (e.g. forward) the first message to the selected gNB-CU (e.g.the first gNB-CU and/or the second gNB-CU). In an example, based on theselection of a gNB-CU based on the first message and/or one or moreelements of the first message, the gNB-DU may transmit (e.g. forward)one or more elements of the first message to the selected gNB-CU (e.g.the first gNB-CU and/or the second gNB-CU). In an example, the gNB-DUmay transmit, to the selected gNB-CU, the first message and/or the oneor more elements of the first message via an F1 interface (e.g. at leastone of the at least one first F1 interface (the first F1-CP) and/or theat least one second F1 interface (the second F1-CP). In an example, theF1 interface may comprise a F1 control plane interface. In an example,if the selected gNB-CU is the first gNB-CU, the gNB-DU may transmit(forward) the first message and/or the one or more elements of the firstmessage to the first gNB-CU via the at least one first F1 interface(e.g. the first F1-CP). In an example, if the selected gNB-CU is thesecond gNB-CU, the gNB-DU may transmit (forward) the first messageand/or the one or more elements of the first message to the secondgNB-CU via the at least one second F1 interface (e.g. the second F1-CP).

In an example, the gNB-DU may transmit, to the selected gNB-CU (e.g. thefirst gNB-CU and/or the second gNB-CU), the first message and/or the oneor more elements of the first message via one or more first F1 messages.In an example, the one or more first F1 messages may comprise at leastone of an uplink (UL) RRC message transfer message, an initial UEcontext setup request message, an initial UE context message, a UEcontext setup response message, a UE context setup failure message, a UEcontext release request message, a UE context release complete message,a UE context modification response message, a UE context modificationfailure message, a UE context modification required message, an F1message transmitted from the gNB-DU to the selected gNB-CU, and/or thelike.

In an example, the one or more first F1 messages may comprise at leastone of the first message, one or more elements of the first message, aUE identifier of the wireless device (e.g. gNB-CU UE F1-AP ID, gNB-DU UEF1AP ID, old gNB-DU UE F1 AP ID, IMSI, TMSI, S-TMSI, C-RNTI, and/or thelike), the resume identifier (ID) received via the first message, asignaling radio bearer (SRB) identifier associated with the firstmessage, an RRC container comprising the first message and/or one ormore elements of the first message, DU to CU RRC information, one ormore success (accepted) bearer identifiers of one or more success(accepted) bearers (e.g. data radio bearers (DRBs), and/or signalingradio bearers (SRBs)) to setup/modify, one or more downlink tunnelendpoint identifiers (e.g. TEID, GTP TEID) for the one or more success(accepted) bearers, one or more failed bearer identifiers of one or morefailed bearers (e.g. data radio bearers (DRBs), and/or signaling radiobearers (SRBs)) to setup/modify, cause information of the one or morefailed bearers, one or more success (accepted) cell identifiers of oneor more success (accepted) cells (e.g. secondary cells, secondary cellgroup, a SpCell, a master cell, PUCCH secondary cells, a PUCCH cell,and/or the like) to setup/modify, one or more failed cell identifiers ofone or more failed cells (e.g. secondary cells, secondary cell group, aSpCell, a master cell, PUCCH secondary cells, a PUCCH cell, and/or thelike) to setup/modify, cause information of the one or more failedcells, a resource coordination transfer container, one or more beareridentifiers of one or more bearers (e.g. data radio bearers (DRBs),and/or signaling radio bearers (SRBs)) required to be modified/released,cause information of the one or more bearers required to bemodified/released, one or more cell identifiers of one or more cells(e.g. secondary cells, secondary cell group, a SpCell, a master cell,PUCCH secondary cells, a PUCCH cell, and/or the like) required to bemodified/released, cause information of the one or more cells requiredto be modified/released, and/or the like.

In an example, in response to receiving the first message and/or the oneor more elements of the first message from the gNB-DU via the F1interface and/or via the one or more first F1 messages, the selectedgNB-CU (e.g. the first gNB-CU and/or the second gNB-CU) may transmit, tothe gNB-DU and via the F1 interface and/or via one or more second F1messages, a response message comprising a downlink RRC message and/orone or more elements for a downlink RRC message associated with thewireless device. In an example, the one or more second F1 messages maycomprise at least one of a downlink (DL) RRC message transfer message,an initial UE context setup response message, an initial UE contextmessage, a UE context setup request message, a UE context releasecommand message, a UE context modification request message, a UE contextmodification confirm message, an F1 message transmitted from theselected gNB-CU to the gNB-DU, and/or the like. In an example, theselected gNB-CU may configure the response message and/or one or moreelements of the response message based on the first message and/or theone or more elements of the first message.

In an example, the one or more second F1 messages may comprise at leastone of the response message (e.g. the downlink RRC message), one or moreelements of the response message (e.g. the downlink RRC message), a UEidentifier of the wireless device (e.g. gNB-CU UE F1-AP ID, gNB-DU UEF1AP ID, old gNB-DU UE F1 AP ID, IMSI, TMSI, S-TMSI, C-RNTI, and/or thelike), a signaling radio bearer (SRB) identifier associated with theresponse message, an RRC container comprising the response messageand/or one or more elements of the response message, CU to DU RRCinformation, one or more bearer identifiers of one or more bearers (e.g.data radio bearers (DRBs), and/or signaling radio bearers (SRBs)) tosetup/modify, one or more uplink tunnel endpoint identifiers (e.g. TEID,GTP TEID) for the one or more bearers, one or more release beareridentifiers of one or more release bearers (e.g. data radio bearers(DRBs), and/or signaling radio bearers (SRBs)) to release, causeinformation of the one or more release bearers, one or more cellidentifiers of one or more cells (e.g. secondary cells, secondary cellgroup, a SpCell, a master cell, PUCCH secondary cells, a PUCCH cell,and/or the like) to setup/modify, one or more release cell identifiersof one or more release cells (e.g. secondary cells, secondary cellgroup, a SpCell, a master cell, PUCCH secondary cells, a PUCCH cell,and/or the like) to release, cause information of the one or morerelease cells, a resource coordination transfer container, and/or thelike.

In an example, the response message (e.g. the downlink RRC message) maycomprise at least one of a counter check message, a downlink informationtransfer message, a handover from NR/EUTRA preparation request message,a logged measurement configuration message, a master information blockmessage, a master information block MBMS message, an MBMS countingrequest, an MBSFN area configuration message, a mobility from NR/EUTRAcommand message, a paging message, a relay node reconfiguration message,an RRC connection reconfiguration message, an RRC connectionreestablishment message, an RRC connection reestablishment rejectmessage, an RRC connection release message, an RRC connection resumemessage, an RRC connection setup message, an SCPTM configuration (e.g.BR) message, a security mode command message, a system informationblock, a system information block type 1, a system information blocktype 1 MBMS, a UE capability inquiry message, a UE information requestmessage, and/or an RRC message associated with the wireless device. Inan example, the gNB-DU may transmit/forward the response message and/orone or more elements of the response message (e.g. the downlink RRCmessage) to the wireless device via radio interface.

In an example, the response message may comprise at least one of anrrc-transactionidentifier information element (IE), a radio resourceconfiguration dedicated IE comprising one or more radio resourceconfiguration parameters, measurement configuration parameters, mobilitycontrol information parameters, one or more NAS layer parameters,security parameters, antenna information parameters, secondary celladdition/modification parameters, secondary cell release parameters,WLAN configuration parameters, WLAN offloading configuration parameters,LWA configuration parameters, LWIP configuration parameters, RCLWIconfiguration parameters, sidelink configuration parameters, V2Xconfiguration parameters, uplink transmission power configurationparameters (e.g. p-MAX, p-MeNB, p-SeNB), a power control modeinformation element, secondary cell group configuration parameters,and/or the like.

In an example, the selected gNB-CU (e.g. the first gNB-CU and/or thesecond gNB-CU) may configure one or more elements of the responsemessage. In an example, the gNB-DU may configure one or more elements ofthe response message. In an example, based on the first message, theselected gNB-CU may transmit a message to the gNB-DU to configure one ormore radio configuration parameters (e.g. physical layerresource/power/cell configuration parameters, and/or RLC/MAC layerconfiguration parameters associated with resource/power/cell) for thewireless device, and/or may receive, from the gNB-DU, the one or moreradio configuration parameters configured by the gNB-DU. The one or moreradio configuration parameters configured by the gNB-DU may be added tothe response message.

In an example, the selected gNB-CU and/or the gNB-DU may configure/applyone or more parameters associated with the wireless device and/or toserve the wireless device, e.g. based on the first message and/or theresponse message. The one or more parameters may comprise at least oneof configuration parameters for an F1 bearer/logical channel, radioresource parameters (e.g. for SDAP, RRC, RLC, MAC, PHY, and/or thelike), security parameters, NG interface session parameters (e.g. PDUsessions, QoS flows, network slices, and/or the like), resourcescheduling parameters, priority management parameters, service policyrelated parameters, and/or the like. In an example, the response message(transmitted to the wireless device) for the first message may comprisethe one or more parameters. In an example, the selected gNB-CU (e.g. thefirst gNB-CU and/or the second gNB-CU) and/or the gNB-DU may serve thewireless device based on the one or more parameters. In an example, theselected gNB-CU (e.g. the first gNB-CU and/or the second gNB-CU) and/orthe gNB-DU may transmit (forward)/receive packets (e.g. PDCP packets)to/from the wireless device via radio interface and/or the F1 interface(e.g. F1 user plane interface (e.g. configured bearers/logicalchannels), F1 control plane interface, and/or the like). In an example,if the selected gNB-CU is the first gNB-CU (e.g. the first PLMN),packets (e.g. PDCP packets, PDCP SDU, SDAP SDU, data, and/or the like)associated with the wireless device may be received/transmitted(forwarded) by a first core network (e.g. UPF, SGW, PGW, and/or thelike) of the first PLMN (e.g. first service operator). In an example, ifthe selected gNB-CU is the second gNB-CU (e.g. the second PLMN), packets(e.g. PDCP packets, PDCP SDU, SDAP SDU, data, and/or the like)associated with the wireless device may be received/transmitted(forwarded) by a second core network (e.g. UPF, SGW, PGW, and/or thelike) of the second PLMN (e.g. second service operator).

In an example, if the first message comprises an RRC connection requestmessage, the gNB-DU may receive, from the first gNB-CU and/or the secondgNB-CU, an RRC connection setup message in response to the RRCconnection request message. In an example, the gNB-DU mayforward/transmit the RRC connection setup message to the wirelessdevice, and/or may receive an RRC connection setup complete message inresponse to transmitting the RRC connection setup message. The gNB-DUmay transmit/forward the RRC connection setup complete message to thegNB-CU. In an example, if the first message comprises an RRC connectionresume request message, the gNB-DU may receive, from the first gNB-CUand/or the second gNB-CU, an RRC connection resume message in responseto the RRC connection resume request message. In an example, the gNB-DUmay forward/transmit the RRC connection resume message to the wirelessdevice, and/or may receive an RRC connection resume complete message inresponse to transmitting the RRC connection resume message. The gNB-DUmay transmit/forward the RRC connection resume complete message to thegNB-CU.

In an example, in response to/based on receiving the first message (e.g.the RRC connection request message/the RRC connection setup completemessage; and/or the RRC connection resume request message/the RRCconnection resume complete message) comprising at least one of the firstPLMN identifier, the first cell identifier (and/or the third cellidentifier), the first gNB identifier, the first gNB-CU identifier, thefirst TAC, the first TAI, the first RAC, the first RAI, the first RNAidentifier, the first RAN area identifier, the first resume identifier,and/or the like (e.g. indicating that the wireless device is allowed(and/or accessible, able, authorized) to access to (and/or employ) thefirst PLMN and/or the serving cell), the first gNB and/or the basestation (e.g. comprising the gNB-DU) may transmit, to a core networkentity (e.g. AMF, MME) of the first PLMN, an NG interface message (e.g.an initial UE message, and/or one or more UE context configurationrelated messages) to configure UE context with one or more core networkentities (e.g. AMF, MME, UPF, SGW, PGW).

In an example, in response to/based on receiving the first message (e.g.the RRC connection request message/the RRC connection setup completemessage; and/or the RRC connection resume request message/the RRCconnection resume complete message) comprising at least one of the firstPLMN identifier, the third cell identifier (and/or the first cellidentifier), the first gNB identifier, the first gNB-CU identifier, thethird TAC, the third TAI, the third RAC, the third RAI, the third RNAidentifier, the third RAN area identifier, the third resume identifier,and/or the like (e.g. indicating that the wireless device is allowed(and/or accessible, able, authorized) to access to (and/or employ) thefirst gNB-CU/the first gNB/the first PLMN and/or the serving cell), thefirst gNB and/or the base station (e.g. comprising the gNB-DU) maytransmit, to a core network entity (e.g. AMF, MME) of the first PLMN, anNG interface message (e.g. an initial UE message, and/or one or more UEcontext configuration related messages) to configure UE context with oneor more core network entities (e.g. AMF, MME, UPF, SGW, PGW).

In an example, in response to/based on receiving the first message (e.g.the RRC connection request message/the RRC connection setup completemessage; and/or the RRC connection resume request message/the RRCconnection resume complete message) comprising at least one of thesecond PLMN identifier, the second cell identifier (and/or the fourthcell identifier), the second gNB identifier, the second gNB-CUidentifier, the second TAC, the second TAI, the second RAC, the secondRAI, the second RNA identifier, the second RAN area identifier, thesecond resume identifier, and/or the like (e.g. indicating that thewireless device is allowed (and/or accessible, able, authorized) toaccess to (and/or employ) the second PLMN and/or the serving cell), thesecond gNB and/or the base station (e.g. comprising the gNB-DU) maytransmit, to a core network entity (e.g. AMF, MME) of the second PLMN,an NG interface message (e.g. an initial UE message, and/or one or moreUE context configuration related messages) to configure UE context withone or more core network entities (e.g. AMF, MME, UPF, SGW, PGW).

In an example, in response to/based on receiving the first message (e.g.the RRC connection request message/the RRC connection setup completemessage; and/or the RRC connection resume request message/the RRCconnection resume complete message) comprising at least one of thesecond PLMN identifier, the fourth cell identifier (and/or the secondcell identifier), the second gNB identifier, the second gNB-CUidentifier, the fourth TAC, the fourth TAI, the fourth RAC, the fourthRAI, the fourth RNA identifier, the fourth RAN area identifier, thefourth resume identifier, and/or the like (e.g. indicating that thewireless device is allowed (and/or accessible, able, authorized) toaccess to (and/or employ) the second gNB-CU/the second gNB/the secondPLMN and/or the serving cell), the second gNB and/or the base station(e.g. comprising the gNB-DU) may transmit, to a core network entity(e.g. AMF, MME) of the second PLMN, an NG interface message (e.g. aninitial UE message, and/or one or more UE context configuration relatedmessages) to configure UE context with one or more core network entities(e.g. AMF, MME, UPF, SGW, PGW).

In an example, in response to/based on receiving the first message, thebase station (e.g. the gNB, the first gNB, the second gNB) may select acore network entity (e.g. AMF, MME) based on the serving cell via whichthe wireless device transmits the first message to the base station(e.g. the gNB, the first gNB, the second gNB, the gNB-DU).

In an example, if the base station receives the first message via theone or more first serving cells (e.g. supporting the first PLMN and/orthe first gNB-CU/the first gNB), the base station may select a corenetwork entity (e.g. AMF, MME) of the first PLMN and/or transmit, to theselected core network entity of the first PLMN, an NG interface message(e.g. an initial UE message, and/or one or more UE context configurationrelated messages) to configure UE context with one or more core networkentities (e.g. AMF, MME, UPF, SGW, PGW).

In an example, if the base station receives the first message via theone or more second serving cells (e.g. supporting the second PLMN and/orthe second gNB-CU/the second gNB), the base station may select a corenetwork entity (e.g. AMF, MME) of the second PLMN and/or transmit, tothe selected core network entity of the second PLMN, an NG interfacemessage (e.g. an initial UE message, and/or one or more UE contextconfiguration related messages) to configure UE context with one or morecore network entities (e.g. AMF, MME, UPF, SGW, PGW).

In an example, if the gNB-DU receives the first message via the one ormore third serving cells (e.g. supporting the first PLMN and the secondPLMN; and/or supporting the first gNB-CU/the first gNB and the secondgNB-CU/the second gNB), the base station may select at least one corenetwork entity (e.g. AMF, MME) of the first PLMN and/or the second PLMNand/or transmit, to the at least one selected core network entity of thefirst PLMN and/or the second PLMN, an NG interface message (e.g. aninitial UE message, and/or one or more UE context configuration relatedmessages) to configure UE context with one or more core network entities(e.g. AMF, MME, UPF, SGW, PGW).

In an example, a base station distributed unit may receive, from a firstbase station central unit, a first message comprising a first publicland mobile network (PLMN) identifier of a first PLMN supported by thefirst base station central unit. The base station distributed unit mayreceive from a second base station central unit, a second messagecomprising a second PLMN identifier of a second PLMN supported by thesecond base station central unit. In an example, the base stationdistributed unit may transmit (e.g. broadcast) at least one thirdmessage comprising the first PLMN identifier and the second PLMNidentifier. The base station distributed unit may receive, from awireless device, a fourth message comprising one of the first PLMNidentifier or the second PLMN identifier. The base station distributedunit may select one of the first base station central unit and thesecond base station central unit as a selected one based on the one ofthe first PLMN identifier or the second PLMN identifier. The selectedone may support a PLMN of the one of the first PLMN identifier or thesecond PLMN identifier PLMN. The base station distributed unit mayforward the fourth message to the selected one.

In an example, the first message and/or the second message may compriseat least one of an F1 setup response message, a base station centralunit configuration update message, and/or a base station distributedunit configuration update acknowledge message. In an example, the basestation distributed unit may transmit, to the first base station centralunit, a fifth message indicating a first F1 setup request, and/or thefirst message may be response for the fifth message. The base stationdistributed unit may transmit, to the second base station central unit,a sixth message indicating a second F1 setup request, and/or the secondmessage may be response for the sixth message.

In an example, the base station distributed unit may transmit to thefirst base station central unit and/or in response to receiving thefirst message, a seventh message indicating a first base station centralunit configuration update acknowledge. In an example, the base stationdistributed unit may transmit to the second base station central unitand/or in response to receiving the second message, an eighth messageindicating a second base station central unit configuration updateacknowledge. In an example, the at least one third message may comprisea system information block (e.g. system information block type 1). In anexample, the base station distributed unit may transmit, to the firstbase station central unit and/or the second base station central unit, asystem information block comprising at least one of the first PLMNidentifier and/or the second PLMN identifier. The base stationdistributed unit may receive the at least one third message from thefirst base station central unit and/or the second base station centralunit, and/or the at least one third message may comprise the systeminformation block (e.g. system information block type 1). In an example,the fourth message may comprise a radio resource control message. In anexample, the base station distributed unit may transmit the at least onethird message via a first cell supporting at least one of the first PLMNand/or the second PLMN. In an example, the base station distributed unitmay transmit first one of the at least one third message via a secondcell, the first one comprising the first PLMN identifier. In an example,the base station distributed unit may transmit second one of the atleast one third message via a third cell, the second one comprising thesecond PLMN identifier.

In an example, the base station distributed unit may receive, from thesecond base station central unit, one or more second configurationparameters associated with the second base station central unit and/orthe second PLMN. The base station distributed unit may transmit, to thefirst base station central unit, the one or more second configurationparameters. The base station distributed unit may receive, from thefirst base station central unit, at least one system information blockcomprising at least one of: one or more first configuration parameters(e.g. and/or a first system information block) associated with the firstbase station central unit and/or the first PLMN; and/or the one or moresecond configuration parameters (e.g. and/or a second system informationblock) associated with the second base station central unit and/or thesecond PLMN. The base station distributed unit may transmit(forward/broadcast) the at least one system information block. The basestation distributed unit may transmit, to the second base stationcentral unit, the at least one system information block.

In an example, the base station distributed unit may receive, from thefirst base station central unit, at least one system information blockcomprising at least one of: one or more first configuration parameters(e.g. and/or a first system information block) associated with the firstbase station central unit and/or the first PLMN; and/or one or moresecond configuration parameters (e.g. and/or a second system informationblock) associated with the second base station central unit and/or thesecond PLMN. The first base station central unit may receive the one ormore second configuration parameters from the second base stationcentral unit (e.g. via an interface between the first gNB-CU and thesecond gNB-CU). The base station distributed unit may transmit(forward/broadcast) the at least one system information block. In anexample, the base station distributed unit may transmit, to the secondbase station central unit, the at least one system information block.

In an example, the base station distributed unit may receive, from thefirst base station central unit, one or more first configurationparameters associated with the first base station central unit and/orthe first PLMN. The base station distributed unit may receive, from thesecond base station central unit, one or more second configurationparameters associated with the second base station central unit and/orthe second PLMN. The base station distributed unit may determine atleast one system information block comprising at least one of: the oneor more first configuration parameters (e.g. and/or a first systeminformation block) associated with the first gNB-CU and/or the firstPLMN; and/or the one or more second configuration parameters (e.g.and/or a second system information block) associated with the secondbase station central unit and/or the second PLMN. (In an example, thebase station distributed unit may transmit, to the first base stationcentral unit and/or the second base station central unit, the at leastone system information block. The base station distributed unit mayreceive, from the first base station central unit and/or the second basestation central unit, the at least one system information block.) In anexample, the base station distributed unit may transmit(forward/broadcast) the at least one system information block.

In an example, the base station distributed unit may receive, from thefirst base station central unit, at least one of: one or more firstconfiguration parameters associated with the first base station centralunit and/or the first PLMN; and/or one or more second configurationparameters associated with the second base station central unit and/orthe second PLMN. The first base station central unit may receive the oneor more second configuration parameters from the second base stationcentral unit. The base station distributed unit may determine at leastone system information block comprising the one or more firstconfiguration parameters (e.g. and/or a first system information block)associated with the first base station central unit and/or the firstPLMN and/or the one or more second configuration parameters (e.g. and/ora second system information block) associated with the second basestation central unit and/or the second PLMN. (In an example, the basestation distributed unit may transmit, to the first base station centralunit and/or the second base station central unit, the at least onesystem information block. The base station distributed unit may receive,from the first base station central unit and/or the second base stationcentral unit, the at least one system information block.) In an example,the base station distributed unit may transmit (forward/broadcast) theat least one system information block.

In an example, the base station distributed unit may receive, from thesecond base station central unit, one or more second configurationparameters associated with the second base station central unit and/orthe second PLMN. The base station distributed unit may transmit, to thefirst base station central unit, the one or more second configurationparameters. The base station distributed unit may receive, from thefirst base station central unit, at least one system information blockcomprising one or more configuration parameters associated with thefirst PLMN and/or the second PLMN (and/or associated with the first basestation central unit and/or the second base station central unit). Thebase station distributed unit may transmit (forward/broadcast) the atleast one system information block. The base station distributed unitmay transmit, to the second base station central unit, the at least onesystem information block.

In an example, the base station distributed unit may receive, from thefirst base station central unit, at least one system information blockcomprising one or more configuration parameters associated with thefirst PLMN and/or the second PLMN (and/or associated with the first basestation central unit and/or the second base station central unit). Thebase station distributed unit may transmit (forward/broadcast) the atleast one system information block. The base station distributed unitmay transmit, to the second base station central unit, the at least onesystem information block.

In an example, the base station distributed unit may receive, from thefirst base station central unit, one or more first configurationparameters associated with the first base station central unit and/orthe first PLMN, and/or may receive, from the second base station centralunit, one or more second configuration parameters associated with thesecond base station central unit and/or the second PLMN. In an example,the base station distributed unit may determine, based on the one ormore first configuration parameters and/or the one or more secondconfiguration parameters, at least one system information blockcomprising one or more configuration parameters associated with thefirst PLMN and/or the second PLMN (and/or associated with the first basestation central unit and/or the second base station central unit). (Inan example, the base station distributed unit may transmit, to the firstbase station central unit and/or the second base station central unit,the at least one system information block. The base station distributedunit may receive, from the first base station central unit and/or thesecond base station central unit, the at least one system informationblock.) In an example, the base station distributed unit may transmit(forward/broadcast) the at least one system information block.

In an example, the base station distributed unit may receive, from thefirst base station central unit, at least one of: one or more firstconfiguration parameters associated with the first base station centralunit and/or the first PLMN; and/or one or more second configurationparameters associated with the second base station central unit or thesecond PLMN. The first base station central unit may receive the one ormore second configuration parameters from the second base stationcentral unit. The base station distributed unit may determine, based onthe one or more first configuration parameters and/or the one or moresecond configuration parameters, at least one system information blockcomprising one or more configuration parameters associated with thefirst PLMN and/or the second PLMN (or associated with the first basestation central unit and/or the second base station central unit). (Inan example, the base station distributed unit may transmit, to the firstbase station central unit and/or the second base station central unit,the at least one system information block. The base station distributedunit may receive, from the first base station central unit and/or thesecond base station central unit, the at least one system informationblock.) In an example, the base station distributed unit may transmit(forward/broadcast) the at least one system information block.

In an example, a base station distributed unit may transmit, to a firstbase station central unit, a first message indicating a first interfacesetup request. The base station distributed unit may receive, from thefirst base station central unit in response to the first message, asecond message indicating a first interface setup response. The secondmessage may comprise a first public land mobile network (PLMN)identifier of a first PLMN supported by the first base station centralunit. The base station distribute unit may transmit, to a second basestation central unit, a third message indicating a second interfacesetup request. The base station distributed unit may receive, from thesecond base station central unit in response to the third message, afourth message indicating a second interface setup response. The fourthmessage may comprise a second PLMN identifier of a second PLMN supportedby the second base station central unit. In an example, the base stationdistributed unit may transmit, to the first base station central unit, afifth message comprising a system information block for a cell of thebase station distributed unit. The system information block may comprisethe first PLMN identifier and the second PLMN identifier. In an example,the base station distributed unit may transmit, to the second basestation central unit, a sixth message comprising the system informationblock for the cell of the base station distributed unit. The systeminformation block may comprise the first PLMN identifier and the secondPLMN identifier.

In an example, a base station distributed unit may establish interfaceconnections with a plurality of base station central units comprising afirst base station central unit of a first public land mobile network(PLMN) and/or a second base station central unit of a second PLMN. Thebase station distributed unit may transmit to a wireless device arandom-access response in response to receiving one or morerandom-access preambles (e.g. via a cell). The base station distributedunit may receive, from the wireless device and/or in response to therandom-access response, a first message comprising a first PLMNidentifier of the first PLMN. The base station distributed unit mayselect the first base station central unit based on the first PLMNidentifier. The base station distributed unit may transmit/forward, tothe first base station central unit, the first message in response toselecting the first base station central unit. In an example, the basestation distributed unit may transmit/broadcast at least one systeminformation block comprising at least one of the first PLMN identifierof the first PLMN and/or a second PLMN identifier of the second PLMN. Inan example, the base station distributed unit may transmit/broadcast theat least on system information block via a cell shared by the first PLMNand the second PLMN. In an example, the wireless device may transmit theone or more random-access preambles to the base station distributed unitbased on the at least one system information block.

In an example, the base station distributed unit may receive, from thefirst base station central unit, a response message for the firstmessage. The base station distributed unit may transmit/forward, to thewireless device, the response message. In an example, the responsemessage may comprise at least one of a radio resource control connectionsetup message and/or a radio resource control connection resume message.In an example, the first message may comprise a radio resource controlmessage. In an example, the first message may comprise at least one of aradio resource control connection request message and/or a radioresource control connection resume request message. In an example, thefirst message may comprise a wireless device identifier of the wirelessdevice. In an example, the wireless device may be allowed to access tothe first PLMN. In an example, the wireless device may have one or morePLMN identifiers of one or more PLMNs allowed to access. The one or morePLMN identifiers may comprise the first PLMN identifier. In an example,the interface connections may comprise at least one of an F1 controlplane interface and/or an F1 user plane interface.

In an example, the base station distributed unit may receive, from asecond wireless device, a second message comprising a second PLMNidentifier of the second PLMN. The base station distributed unit mayselect the second base station central unit based on the second PLMNidentifier. The base station distributed unit may transmit/forward, tothe second base station central unit, the second message in response toselecting the second base station central unit. In an example, the basestation distribute unit may receive, from the wireless device, the oneor more random-access preambles via the cell. In an example, the cellmay be shared by the first PLMN and the second PLMN. In an example, thebase station distributed unit may receive, from the wireless device, oneor more radio resource control messages comprising at least one of: awireless device identifier of the wireless device (e.g. C-RNTI); a firstcell identifier of the cell (e.g. the cell identifier may be associatedwith the first PLMN); a first base station central unit identifier ofthe first base station central unit; a first base station identifier ofthe first base station central unit; a first tracking area code of thecell for the first PLMN; and/or the first PLMN identifier. The basestation distributed unit may select the first base station central unitbased on at least one of: the wireless device identifier (e.g. C-RNTI);the first cell identifier of the cell; the first base station centralunit identifier; the first base station identifier; the first trackingarea code; and/or the first PLMN identifier. The base stationdistributed unit may transmit/forward, to the first base station centralunit, the one or more radio resource control messages.

In an example, a base station distributed unit may establish interfaceconnections with a plurality of base station central units comprising afirst base station central unit of a first public land mobile network(PLMN) and/or a second base station central unit of a second PLMN. Thebase station distributed unit may transmit, to a wireless device, arandom-access response in response to receiving one or morerandom-access preambles. The base station distributed unit may receive,from the wireless device and/or in response to the random-accessresponse, a first message comprising a first cell identifier of a cell.The first cell identifier may be for the first PLMN. The base stationdistributed unit may select the first base station central unit based onthe first cell identifier. The base station distributed unit maytransmit/forward, to the first base station central unit, the firstmessage in response to selecting the first base station central unit. Inan example, the base station distributed unit may transmit/broadcast atleast one system information block comprising at least one of: the firstcell identifier of the cell; a second cell identifier of the cell (e.g.the second cell identifier may be for the second PLMN); a first PLMNidentifier of the first PLMN; and/or a second PLMN identifier of thesecond PLMN.

In an example, the base station distribute unit may transmit/broadcastthe at least on system information block via the cell. In an example,the wireless device may transmit the one or more random-access preamblesto the base station distributed unit based on the at least one systeminformation block. In an example, the base station distributed unit mayreceive, from the first base station central unit, a response messagefor the first message. The base station distributed unit maytransmit/forward, to the wireless device, the response message. In anexample, the response message may comprise at least one of a radioresource control connection setup message and/or a radio resourcecontrol connection resume message. In an example, the first message maycomprise a radio resource control message. In an example, the firstmessage may comprise at least one of a radio resource control connectionrequest message (e.g. message 3) and/or a radio resource controlconnection resume request message. In an example, the first message maycomprise a wireless device identifier of the wireless device. In anexample, the wireless device may be allowed to access to the first PLMN.In an example, the wireless device may have one or more PLMN identifiersof one or more PLMNs allowed to access. The one or more PLMN identifiersmay comprise a first PLMN identifier of the first cell identifier of thecell. In an example, the interface connections may comprise at least oneof an F1 control plane interface and/or an F1 user plane interface.

In an example, the base station distributed unit may receive, from asecond wireless device, a second message comprising a second cellidentifier of the cell. The second cell identifier may be for the secondPLMN. The base station distributed unit may select the second basestation central unit based on the second cell identifier. The basestation distributed unit may transmit/forward, to the second basestation central unit, the second message in response to selecting thesecond base station central unit. In an example, the base stationdistribute unit may receive, from the wireless device, the one or morerandom-access preambles via the cell. In an example, the cell may beshared by the first PLMN and the second PLMN.

In an example, a base station distributed unit may establish interfaceconnections with a plurality of base station central units comprising afirst base station central unit of a first public land mobile network(PLMN) and/or a second base station central unit of a second PLMN. Thebase station distributed unit may transmit, to a wireless device, arandom-access response in response to receiving one or morerandom-access preambles via a cell. The base station distributed unitmay receive, from the wireless device and/or in response to therandom-access response, a first message comprising a first indicationparameter. The base station distributed unit may select the first basestation central unit based on the first indication parameter. The basestation distributed unit may transmit/forward, to the first base stationcentral unit, the first message in response to selecting the first basestation central unit. In an example, the first indication parameter maycomprise at least one of: a first PLMN identifier of the first PLMN; afirst cell identifier of the cell (e.g. the first cell identifier may befor the first PLMN); a first tracking area code of the cell (e.g. thefirst tracking area code may be for the first PLMN); a first trackingarea identifier of the cell (e.g. the first tracking area identifier maybe for the first PLMN); a first registration area code of the cell (e.g.the first registration area code may be for the first PLMN); a firstregistration area identifier of the cell (e.g. the first registrationarea identifier may be for the first PLMN); a first base stationidentifier of the first base station central unit; and/or a first basestation central unit identifier of the first base station central unit.

In an example, the base station distributed unit may transmit/broadcastat least one system information block comprising at least one of: afirst PLMN identifier of the first PLMN; a first cell identifier of thecell (e.g. the first cell identifier may be for the first PLMN); a firsttracking area code of the cell (e.g. the first tracking area code may befor the first PLMN); a first tracking area identifier of the cell (e.g.the first tracking area identifier may be for the first PLMN); a firstregistration area code of the cell (e.g. the first registration areacode may be for the first PLMN); a first registration area identifier ofthe cell (e.g. the first registration area identifier may be for thefirst PLMN); a first base station identifier of the first base stationcentral unit; a first base station central unit identifier of the firstbase station central unit; a second PLMN identifier of the second PLMN;a second cell identifier of the cell (e.g. the second cell identifiermay be for the second PLMN); a second tracking area code of the cell(e.g. the second tracking area code may be for the second PLMN); asecond tracking area identifier of the cell (e.g. the second trackingarea identifier may be for the second PLMN); a second registration areacode of the cell (e.g. the second registration area code may be for thesecond PLMN); a second registration area identifier of the cell (e.g.the second registration area identifier may be for the second PLMN); asecond base station identifier of the second base station central unit;and/or a second base station central unit identifier of the second basestation central unit.

In an example, the base station distribute unit may transmit/broadcastthe at least on system information block via the cell. The wirelessdevice may transmit the one or more random-access preambles to the basestation distributed unit based on the at least one system informationblock. In an example, the base station distribute unit may receive, fromthe first base station central unit, a response message for the firstmessage. The base station distributed unit may transmit/forward, to thewireless device, the response message. The response message may compriseat least one of a radio resource control connection setup message and/ora radio resource control connection resume message. In an example, thefirst message may comprise a radio resource control message. In anexample, the first message may comprise at least one of a radio resourcecontrol connection request message (e.g. message 3) and/or a radioresource control connection resume request message. In an example, thefirst message further may comprise a wireless device identifier of thewireless device. In an example, the wireless device may be allowed toaccess to the first PLMN.

In an example, the wireless device may have one or more PLMN identifiersof one or more PLMNs allowed to access. The one or more PLMN identifiersmay comprise a first PLMN identifier associated with the firstindication parameter. The interface connections may comprise at leastone of an F1 control plane interface and/or an F1 user plane interface.In an example, the base station distributed unit may receive, from asecond wireless device, a second message comprising a second indicationparameter of the cell. The second cell identifier may be for the secondPLMN. The base station distribute unit may select the second basestation central unit based on the second indication parameter. The basestation distribute unit may transmit/forward, to the second base stationcentral unit, the second message in response to selecting the secondbase station central unit. In an example, the base station distributeunit may receive, from the wireless device, the one or morerandom-access preambles via the cell. In an example, the cell may beshared by the first PLMN and the second PLMN.

In an example, a base station may receive, from a wireless device, afirst radio resource control message comprising a first indicationparameter of a cell. The first indication parameter may be associatedwith a first PLMN. The base station may select a core network entitybased on the first indication parameter. The base station may transmit,to the selected core network entity, a first message indicating aninitial access of the wireless device. In an example, the cell may beshared by the first PLMN and a second PLMN. In an example, the basestation may be connected to at least one of a first core network entityof the first PLMN and/or a second core network entity of a second PLMN.In an example, the first indication parameter may comprise at least oneof: a first PLMN identifier of the first PLMN; a first cell identifierof a cell (e.g. the first cell identifier may be for the first PLMN); afirst tracking area code of the cell (e.g. the first tracking area codemay be for the first PLMN); a first tracking area identifier of the cell(e.g. the first tracking area identifier may be for the first PLMN); afirst registration area code of the cell (e.g. the first registrationarea code may be for the first PLMN); a first registration areaidentifier of the cell (e.g. the first registration area identifier maybe for the first PLMN); a first base station identifier of the firstbase station central unit; and/or a first base station central unitidentifier of the first base station central unit.

In an example, the base station may transmit/broadcast at least onesystem information block comprising at least one of: a first PLMNidentifier of the first PLMN; a first cell identifier of the cell (e.g.the first cell identifier may be for the first PLMN); a first trackingarea code of the cell (e.g. the first tracking area code may be for thefirst PLMN); a first tracking area identifier of the cell (e.g. thefirst tracking area identifier may be for the first PLMN); a firstregistration area code of the cell (e.g. the first registration areacode may be for the first PLMN); a first registration area identifier ofthe cell (e.g. the first registration area identifier may be for thefirst PLMN); a first base station identifier of the first base stationcentral unit; a first base station central unit identifier of the firstbase station central unit; a second PLMN identifier of the second PLMN;a second cell identifier of the cell (e.g. the second cell identifiermay be for the second PLMN); a second tracking area code of the cell(e.g. the second tracking area code may be for the second PLMN); asecond tracking area identifier of the cell (e.g. the second trackingarea identifier may be for the second PLMN); a second registration areacode of the cell (e.g. the second registration area code may be for thesecond PLMN); a second registration area identifier of the cell (e.g.the second registration area identifier may be for the second PLMN); asecond base station identifier of the second base station central unit;and/or a second base station central unit identifier of the second basestation central unit. In an example, the wireless device may transmitthe first radio resource control message based on the at least onesystem information block.

Embodiments may be configured to operate as needed. The disclosedmechanism may be performed when certain criteria are met, for example,in a wireless device, a base station, a radio environment, a network, acombination of the above, and/or the like. Example criteria may bebased, at least in part, on for example, wireless device or network nodeconfigurations, traffic load, initial system set up, packet sizes,traffic characteristics, a combination of the above, and/or the like.When the one or more criteria are met, various example embodiments maybe applied. Therefore, it may be possible to implement exampleembodiments that selectively implement disclosed protocols.

A base station may communicate with a mix of wireless devices. Wirelessdevices and/or base stations may support multiple technologies, and/ormultiple releases of the same technology. Wireless devices may have somespecific capability(ies) depending on wireless device category and/orcapability(ies). A base station may comprise multiple sectors. When thisdisclosure refers to a base station communicating with a plurality ofwireless devices, this disclosure may refer to a subset of the totalwireless devices in a coverage area. This disclosure may refer to, forexample, a plurality of wireless devices of a given LTE or 5G releasewith a given capability and in a given sector of the base station. Theplurality of wireless devices in this disclosure may refer to a selectedplurality of wireless devices, and/or a subset of total wireless devicesin a coverage area which perform according to disclosed methods, and/orthe like. There may be a plurality of base stations or a plurality ofwireless devices in a coverage area that may not comply with thedisclosed methods, for example, because those wireless devices or basestations perform based on older releases of LTE or 5G technology.

According to various embodiments, a device such as, for example, awireless device, a base station, base station distributed unit, a basestation central unit, and/or the like, may comprise one or moreprocessors and memory. The memory may store instructions that, whenexecuted by the one or more processors, cause the device to perform aseries of actions. Embodiments of example actions are illustrated in theaccompanying figures and specification. Features from variousembodiments may be combined to create yet further embodiments.

FIG. 43 is an flow diagram as per an aspect of an example embodiment ofthe present disclosure. At 4310, a first message may be received by abase station distributed unit from a first base station central unit.The first message may comprise a first public land mobile network (PLMN)identifier of a first PLMN. The first PLMN may comprise the first basestation central unit. At 4120, the base station distributed unit mayreceive a second message from a second base station central unit. Thesecond message may comprise a second PLMN identifier of a second PLMN.The second PLMN may comprise the second base station central unit. At4130, the base station distributed unit may transmit at least one systeminformation block. The at least one system information block maycomprise the first PLMN identifier and the second PLMN identifier.

According to an example embodiment, the base station distributed unitmay receive a radio resource control message from a wireless device. Theradio resource control message may be based on the at least one systeminformation block. The base station distributed unit may configure radioresources for the wireless device based on the radio resource controlmessage. The wireless device may be associated with the first PLMN. Thewireless device may be associated with the second PLMN.

According to an example embodiment, the base station distributed unitmay receive packets from the first base station central unit. The basestation distributed unit may receive packets from the second basestation central unit. The base station distributed unit may transmit thepackets to a wireless device associated with the first PLMN, The basestation distributed unit may transmit the packets to a wireless deviceassociated with the second PLMN.

According to an example embodiment, the first message and the secondmessage comprise an F1 setup response message. The first message and thesecond message comprise a base station central unit configuration updatemessage. The first message and the second message comprise a basestation distributed unit configuration update acknowledge message.

According to an example embodiment, the base station distributed unitmay transmit a first F1 setup request message to the first base stationcentral unit. The first message may be response for the first F1 setuprequest message. the base station distributed unit may transmit a secondF1 setup request message to the second base station central unit. Thesecond message is response for the second F1 setup request message.

According to an example embodiment, the at least one system informationblock may comprise cell parameters for at least one of the first PLMN orthe second PLMN. The cell parameters may comprise a cell identifier of acell that the at least one system information block is transmitted via.The cell parameters may comprise a closed subscriber group identifier ofthe cell. The cell parameters may comprise a first cell identifier ofthe cell. The first cell identifier may be associated with the firstPLMN. The cell parameters may comprise a second cell identifier of thecell. The second cell identifier may be associated with the second PLMN.The cell parameters may comprise a first closed subscriber groupidentifier of the cell. The first closed subscriber group identifier maybe associated with the first PLMN. The cell parameters may comprise asecond closed subscriber group identifier of the cell. The second closedsubscriber group identifier may be associated with the second PLMN. Thecell parameters may comprise a first base station central unitidentifier of the first base station central unit. The cell parametersmay comprise a second base station central unit identifier of the firstbase station central unit. The cell parameters may comprise a first basestation identifier of a first base station associated with the firstbase station central unit. The cell parameters may comprise a secondbase station identifier of a second base station associated with thesecond base station central unit.

According to an example embodiment, the transmission of the at least onesystem information block may comprise transmitting the at least onesystem information block via a cell that is shared for the first PLMNand the second PLMN. According to an example embodiment, the at leastone system information block may comprise a first system informationblock comprising the first PLMN identifier. The at least one systeminformation block may comprise a second system information blockcomprising the second PLMN identifier.

According to an example embodiment, the first system information blockmay comprise a first cell identifier of a cell. The first cellidentifier may be associated with the first PLMN. The first systeminformation block may comprise a first closed subscriber groupidentifier of the cell. The first closed subscriber group identifier maybe associated with the first PLMN. The first system information blockmay comprise a first base station central unit identifier of the firstbase station central unit. The first system information block maycomprise a first base station identifier of a first base station may beassociated with the first base station central unit. According to anexample embodiment, the first system information block comprise a secondcell identifier of a cell. The second cell identifier may be associatedwith the second PLMN. The first system information block comprise asecond closed subscriber group identifier of the cell. The second closedsubscriber group identifier may be associated with the second PLMN. Thefirst system information block comprise a second base station centralunit identifier of the first base station central unit. The first systeminformation block comprise a second base station identifier of a secondbase station may be associated with the second base station centralunit. According to an example embodiment, the at least one systeminformation block may comprise a first system information block. Thefirst system information block may comprise the first PLMN identifier.

The first system information block may be transmitted via a first cellof the first PLMN. The at least one system information block maycomprise a second system information block comprising the second PLMNidentifier. The second system information block transmitted via a secondcell of the second PLMN. According to an example embodiment, the basestation distributed unit may receive the at least one system informationblock from the first base station central unit. According to an exampleembodiment, the base station distributed unit may transmit configurationparameters to the first base station central unit. The configurationparameters may comprise the second PLMN identifier. The at least onesystem information block may be based on the configuration parameters.According to an example embodiment, the base station distributed unitmay determine the at least one system information block based on thefirst message and the second message. According to an exampleembodiment, the base station distributed unit may transmit the at leastone system information block to at least one of the first base stationcentral unit or the second base station central unit. According to anexample embodiment, the at least one system information block maycomprise a system information block 1. According to an exampleembodiment, a base station may comprise the first base station centralunit, the second base station central unit, and the base stationdistributed unit.

According to an example embodiment, a first base station may comprisethe first base station central unit and the base station distributedunit. A second base station may comprise the second base station centralunit and the base station distributed unit. According to an exampleembodiment, the base station distributed unit may serve a cell shared bythe first PLMN and the second PLMN. The base station distributed unitmay serve a first cell of the first PLMN. The base station distributedunit may serve a second cell of the second PLMN. According to an exampleembodiment, the base station distributed unit may receive a thirdmessage from a third base station central unit. The third message maycomprise a third PLMN identifier of a third PLMN comprising the thirdbase station central unit. The at least one system information block maycomprise the third PLMN identifier.

FIG. 44 is an example flow diagram as per an aspect of an embodiment ofthe present disclosure. At 4410, a shared base station distributed unitmay communicate first packets with a first non-shared base stationcentral unit of a first public land mobile network (PLMN). The firstpackets may be associated with the first PLMN. According to an exampleembodiment, the shared base station distributed unit may be shared bythe first PLMN and a second PLMN. According to an example embodiment, afirst non-shared base station central unit of a first public land mobilenetwork (PLMN) may communicate first packets with a shared base stationdistributed unit. The first packets may be associated with the firstPLMN. According to an example embodiment, the shared base stationdistributed unit may be shared by the first PLMN and a second PLMN.

FIG. 45 is an example flow diagram as per an aspect of an embodiment ofthe present disclosure. At 4510, a base station distributed unit maycommunicate first packets with a first base station central unit of afirst public land mobile network (PLMN). The first packets may beassociated with the first PLMN. The base station distributed unit maycommunicate with a second PLMN. The first base station central unit maynot communicate with the second PLMN. According to an exampleembodiment, the base station distributed unit may be shared by the firstPLMN and the second PLMN. According to an example embodiment, a firstbase station central unit of a first public land mobile network (PLMN)may communicate first packets with a base station distributed unit. Thefirst packets may be associated with the first PLMN. The first basestation central unit may not communicate with a second PLMN. The basestation distributed unit may communicate with the second PLMN. Accordingto an example embodiment, the base station distributed unit may beshared by the first PLMN and the second PLMN.

According to an example embodiment, a base station distributed unit maycommunicate first packets with a first base station central unit of afirst public land mobile network (PLMN). The first packets may beassociated with the first PLMN. The base station distributed unit maycommunicate second packets with a second base station central unit of asecond PLMN. The second packets may be associated with the second PLMN.According to an example embodiment, the base station distributed unitmay determine the first base station central unit for the communicationof the first packets based on the first base station central unit beingassociated with the first PLMN. The base station distributed unit maydetermine the second base station central unit for the communicating thesecond packets based on the second base station central unit beingassociated with the second PLMN. According to an example embodiment, thecommunication of the first packets may comprise transmitting at leastone of the first packets. The communication of the first packets maycomprise receiving at least one of the first packets.

According to an example embodiment, a base station distributed unit maytransmit first packets to a first base station central unit of a firstpublic land mobile network (PLMN). The first packets may be receivedfrom a first wireless device associated with the first PLMN. The basestation distributed unit may transmit second packets to a second basestation central unit of a second PLMN. The second packets may bereceived from a second wireless device associated with the second PLMN.According to an example embodiment, the first packets may comprisecontrol plane packets. The second packets may comprise control planepackets. According to an example embodiment, the first packets maycomprise user plane packets. The second packets may comprise user planepackets.

According to an example embodiment, a base station distributed unit maytransmit at least one system information block. The at least one systeminformation block may comprise a first public land mobile network (PLMN)identifier of a first PLMN. The at least one system information blockmay comprise a second PLMN identifier of a second PLMN. The base stationdistributed unit may communicate first packets with a first base stationcentral unit of the first PLMN. The first packets may be associated withthe first PLMN. The base station distributed unit may communicate secondpackets with a second base station central unit of the second PLMN. Thesecond packets may be associated with the second PLMN.

According to an example embodiment, a base station distributed unit maytransmit at least one system information block. The at least one systeminformation block may comprise a first public land mobile network (PLMN)identifier of a first PLMN. The at least one system information blockmay comprise a second PLMN identifier of a second PLMN. The base stationdistributed unit may transmit first packets to a first base stationcentral unit of the first PLMN. The first packets may be received from afirst wireless device associated with the first PLMN. The base stationdistributed unit may transmit second packets to a second base stationcentral unit of the second PLMN. The second packets may be received froma second wireless device associated with the second PLMN.

According to an example embodiment, a base station distributed unit maycommunicate with a first base station central unit of a first publicland mobile network (PLMN). The base station distributed unit maycommunicate with a second base station central unit of a second PLMN.The base station distributed unit may transmit at least one systeminformation block. The at least one system information block maycomprise a first PLMN identifier of a first PLMN. The at least onesystem information block may comprise a second PLMN identifier of asecond PLMN.

According to an example embodiment, a base station distributed unit mayreceive a first message from a first base station central unit. Thefirst message may comprise a first public land mobile network (PLMN)identifier of a first PLMN comprising the first base station centralunit. The base station distributed unit may receive a second messagefrom a second base station central unit. The second message may comprisea second PLMN identifier of a second PLMN comprising the second basestation central unit. The base station distributed unit may transmitpackets to a wireless device associated with at least one of the firstPLMN and the second PLMN. The packets may be received from at least oneof the first base station central unit and the second base stationcentral unit.

FIG. 46 is an example flow diagram as per an aspect of an embodiment ofthe present disclosure. At 4610, a base station distributed unit mayreceive at least one system information block from a first base stationcentral unit. The at least one system information block may comprise oneor more first configuration parameters associated with the first basestation central unit. The at least one system information block maycomprise one or more second configuration parameters associated with asecond base station central unit. At 4620, the base station distributedunit may transmit the at least one system information block. Accordingto an example embodiment, the first base station central unit may beassociated with a first public land mobile network (PLMN). The secondbase station central unit may be associated with a second PLMN.According to an example embodiment, the one or more first configurationparameters may comprise a first public land mobile network (PLMN)identifier of the first PLMN. The one or more second configurationparameters may comprise a second PLMN identifier of a second PLMN.

FIG. 47 is an example flow diagram as per an aspect of an embodiment ofthe present disclosure. At 4710, a base station distributed unit mayreceive one or more second configuration parameters from a second basestation central unit. The one or more second configuration parametersmay be associated with the second base station central unit. At 4720,the base station distributed unit may transmit the one or more secondconfiguration parameters to a first base station central unit. At 4730,the base station distributed unit may receive at least one systeminformation block from the first base station central unit. The at leastone system information block may comprise one or more firstconfiguration parameters associated with the first base station centralunit. The at least one system information block may comprise the one ormore second configuration parameters. At 4740, the base stationdistributed unit may transmit the at least one system information block.

FIG. 48 is an example flow diagram as per an aspect of an embodiment ofthe present disclosure. At 4810, a first base station central unit mayreceive one or more second configuration parameters from a base stationdistributed unit. The one or more second configuration parameters may beassociated with a second base station central unit. At 4820, the firstbase station central unit may send at least one system information blockto the base station distributed unit. The at least one systeminformation block may comprise one or more first configurationparameters associated with the first base station central unit. The atleast one system information block may comprise the one or more secondconfiguration parameters.

According to an example embodiment, a first base station central unitmay receive one or more second configuration parameters from a secondbase station central unit. The one or more second configurationparameters may be associated with the second base station central unit.The first base station central unit may send at least one systeminformation block to a base station distributed unit. The at least onesystem information block may comprise one or more first configurationparameters associated with the first base station central unit. The atleast one system information block may comprise the one or more secondconfiguration parameters.

FIG. 49 is an example flow diagram as per an aspect of an embodiment ofthe present disclosure. At 4910, a base station distributed unit mayreceive a first message from a first base station central unit. Thefirst message may comprise a first network identifier of a first networkthat the first base station central unit supports. At 4920, a secondmessage may be received from a second base station central unit. Thesecond message may comprise a second network identifier of a secondnetwork that the second base station central unit supports. At 4930, atleast one system information block may be transmitted. The at least onesystem information block may comprise the first network identifier. Theat least one system information block may comprise the second networkidentifier. According to an example embodiment, the first network maycomprise a public land mobile network (PLMN). The first network maycomprise a mobile network. The first network may comprise avehicle-to-everything communication system. The first network maycomprise an intelligent transportation system (ITS). The first networkmay comprise an Internet-of-things (IoT) system. The first network maycomprise satellite network. The second network may comprise a publicland mobile network (PLMN). The second network may comprise a mobilenetwork. The second network may comprise a vehicle-to-everythingcommunication system. The second network may comprise an intelligenttransportation system (ITS). The second network may comprise anInternet-of-things (IoT) system. The second network may comprisesatellite network.

FIG. 50 is an example flow diagram as per an aspect of an embodiment ofthe present disclosure. At 5010, a base station distributed unit maytransmit at least one system information block to a wireless device. Theat least one system information block may indicate a first public landmobile network (PLMN). The at least one system information block mayindicate a second PLMN. At 5020, the base station distributed unit mayreceive a radio resource control message from the wireless device. Theradio resource control message may indicate at least one PLMN of thefirst PLMN and the second PLMN. At 5030, the base station distributedunit may determine, based on the at least one PLMN, at least one basestation central unit from: a first base station central unit of thefirst PLMN; and a second base station central unit of the second PLMN.At 5040, the base station distributed unit may transmit the radioresource control message to the at least one base station central unit.

According to an example embodiment, the radio resource control messagemay comprise a radio resource control complete message. The radioresource control message may comprise a radio resource control requestmessage. The radio resource control message may comprise a radioresource control resume complete message. The radio resource controlmessage may comprise a radio resource control resume request message.According to an example embodiment, the base station distributed unitmay receive from the wireless device, at least one random accesspreamble based on the at least one system information block. The basestation distributed unit may transmit to the wireless device, a randomaccess response for the at least one random access preamble. The radioresource control message may be based on the random access response.

According to an example embodiment, the base station distributed unitmay receive a radio resource control setup message from the at least onebase station central unit. The radio resource control setup message maycomprise cell configuration parameters for the wireless device. Theradio resource control setup message may be a response for the radioresource control message. The base station distributed unit may transmitthe radio resource control setup message to the wireless device.According to an example embodiment, the base station distributed unitmay receive a configuration request message for the wireless device fromthe at least one base station central unit. The base station distributedunit may determine, based on the configuration request message, the cellconfiguration parameters. The base station distributed unit may transmita configuration response message to the at least one base stationcentral unit. The configuration response message may comprise the cellconfiguration parameters. The radio resource control setup message maybe based on the configuration response message.

According to an example embodiment, the base station distributed unitmay receive from the at least one base station central unit, packets forthe wireless device. The base station distributed unit may transmit thepackets to the wireless device. According to an example embodiment, thereceiving of the radio resource control message may comprise receivingthe radio resource control message via a cell that is shared for thefirst PLMN and the second PLMN. According to an example embodiment, thereceiving of the radio resource control message may comprise receivingthe radio resource control message via a first cell of the first PLMN.The receiving of the radio resource control message may comprisereceiving the radio resource control message via a second cell of thesecond PLMN.

According to an example embodiment, the determination of the at leastone base station central unit may be further based on a cell that thebase station distributed unit receives the radio resource controlmessage via. The cell may comprise the first cell. The cell may comprisethe second cell.

According to an example embodiment, the transmission of the at least onesystem information block may comprise transmitting the at least onesystem information block via a cell that is shared for the first PLMNand the second PLMN. The transmission of the at least one systeminformation block may comprise transmitting a first system informationblock comprising a first PLMN identifier of the first PLMN via a firstcell of the first PLMN. The transmission of the at least one systeminformation block may comprise transmitting a second system informationblock comprising a second PLMN identifier of the second PLMN via asecond cell of the second PLMN.

According to an example embodiment, the radio resource control messagemay comprise one or more parameters for the at least one PLMN. The oneor more parameters may comprise at least one PLMN identifier of the atleast one PLMN. The one or more parameters may comprise a cellidentifier of a cell that the base station distributed unit receives theradio resource control message via. The one or more parameters maycomprise a tracking area code of the cell. The one or more parametersmay comprise a registration area code of the cell. The one or moreparameters may comprise a first cell identifier of a first cellassociated with the first PLMN. The one or more parameters may comprisea second cell identifier of a second cell associated with the secondPLMN. The one or more parameters may comprise a base station centralunit identifier of the at least one base station central unit. The oneor more parameters may comprise a base station identifier of a basestation associated with the at least one base station central unit.According to an example embodiment, the determination of the at leastone base station central unit may be further based on the one or moreparameters for the at least one PLMN. According to an exampleembodiment, the at least one system information block may comprise theone or more parameters for the at least one PLMN.

According to an example embodiment, the base station distributed unitmay configure radio resources for the wireless device. According to anexample embodiment, the wireless device may be allowed to access the atleast on PLMN. According to an example embodiment, the at least onesystem information block may comprise a first system information blockcomprising a first PLMN identifier of the first PLMN. The first systeminformation block may be transmitted via a first cell of the first PLMN.According to an example embodiment, the at least one system informationblock may comprise a second system information block comprising a secondPLMN identifier of the second PLMN. The second system information blockmay be transmitted via a second cell of the second PLMN. According to anexample embodiment, the at least one system information block maycomprise a system information block 1. According to an exampleembodiment, a base station may comprise the first base station centralunit. A base station may comprise the second base station central unit.A base station may comprise the base station distributed unit. Accordingto an example embodiment, a first base station may comprise the firstbase station and the base station distributed unit. According to anexample embodiment, a second base station comprise the second basestation and the base station distributed unit. According to an exampleembodiment, the base station distributed unit may serve a cell shared bythe first PLMN and the second PLMN. The base station distributed unitmay serve a first cell of the first PLMN. The base station distributedunit may serve a second cell of the second PLMN. According to an exampleembodiment, the base station distributed unit may receive a second radioresource control message from a second wireless device. The second radioresource control message may indicate a third PLMN. The base stationdistributed unit may determine, based on the third PLMN, a third basestation central unit of the third PLMN. The base station distributedunit may transmit the radio resource control message to the third basestation central unit.

FIG. 51 is an example flow diagram as per an aspect of an embodiment ofthe present disclosure. At 5110, a base station distributed unit mayreceive a radio resource control message from a wireless device. Theradio resource control message may indicate a public land mobile network(PLMN). The PLMN may be one of a first PLMN and a second PLMN. At 5120,the base station distributed unit may determine, based on the PLMN, abase station central unit from: a first base station central unit of thefirst PLMN; and a second base station central unit of the second PLMN.At 5130, the base station distributed unit may transmit the radioresource control message to the base station central unit.

According to an example embodiment, the radio resource control messagemay comprise a first parameter indicating the first PLMN. The firstparameter may comprise a first PLMN identifier. The first parameter maycomprise a first cell identifier of a cell. The first parameter maycomprise a first base station central unit identifier of the first basestation central unit. The first parameter may comprise a first basestation identifier of the first base station central unit. The firstparameter may comprise a first closed subscriber group identifier of acell. The first parameter may comprise a first tracking area code of thecell. The first parameter may comprise a first registration area code ofthe cell.

According to an example embodiment, the radio resource control messagemay comprise a second parameter indicating the second PLMN. The secondparameter may comprise a second PLMN identifier. The second parametermay comprise a second cell identifier of a cell. The second parametermay comprise a second base station central unit identifier of the secondbase station central unit. The second parameter may comprise a secondbase station identifier of the second base station central unit. Thesecond parameter may comprise a second closed subscriber groupidentifier of a cell. The second parameter may comprise a secondtracking area code of the cell. The second parameter may comprise asecond registration area code of the cell.

FIG. 52 is an example flow diagram as per an aspect of an embodiment ofthe present disclosure. At 5210, a base station distributed unit maytransmit at least one system information block to a wireless device. Theat least one system information block may comprise a first public landmobile network (PLMN) identifier of a first base station central unit.The at least one system information block may comprise a second PLMNidentifier of a second base station central unit. At 5220, the basestation distributed unit may receive a radio resource control messagefrom the wireless device. The radio resource control message maycomprise at least one PLMN identifier selected from the first PLMNidentifier and the second PLMN identifier. At 5230, the base stationdistributed unit may select at least one base station central unit fromthe first base station central unit and the second base station centralunit. The selection may be based on the at least one PLMN identifier. At5240, the base station distributed unit may transmit the radio resourcecontrol message to the at least one base station central unit.

According to an example embodiment, a base station distributed unit maytransmit at least one system information block to a wireless device. Theat least one system information block may indicate a first public landmobile network (PLMN). The at least one system information block mayindicate a second PLMN. the base station distributed unit may receive aradio resource control message from the wireless device. The radioresource control message may comprise at least one base station centralunit identifier associated with at least one PLMN of the first PLMN andthe second PLMN. The base station distributed unit may select, based onthe at least one base station central unit identifier, at least one basestation central unit from: a first base station central unit of thefirst PLMN; and a second base station central unit of the second PLMN.The base station distributed unit may transmit the radio resourcecontrol message to the at least one base station central unit. Accordingto an example embodiment, the at least one base station central unitidentifier may indicate the at least one base station central unitsupports the at least one PLMN.

FIG. 53 is an example flow diagram as per an aspect of an embodiment ofthe present disclosure. At 5310, a base station distributed unit maytransmit at least one system information block to a wireless device. Theat least one system information block may indicate a first public landmobile network (PLMN). he at least one system information block mayindicate a second PLMN. At 5320, may receive, by the base stationdistributed unit from the wireless device, a radio resource controlmessage comprising at least one cell identifier of a cell. The at leastone cell identifier may be associated with at least one PLMN of thefirst PLMN and the second PLMN. At 5330, the base station distributedunit may determine, based on the at least one cell identifier, at leastone base station central unit from: a first base station central unit ofthe first PLMN; and a second base station central unit of the secondPLMN. At 5340, the base station distributed unit may transmit the radioresource control message to the at least one base station central unit.

FIG. 54 is an example flow diagram as per an aspect of an embodiment ofthe present disclosure. At 5410, a base station distributed unit maytransmit at least one system information block to a wireless device. Theat least one system information block may indicate a first public landmobile network (PLMN). The at least one system information block mayindicate a second PLMN. At 5420, the base station distributed unit mayreceive a radio resource control message from the wireless device via acell associated with at least one PLMN of the first PLMN and the secondPLMN. At 5430, the base station distributed unit may select, based onthe cell associated with the at least one PLMN, at least one basestation central unit from: a first base station central unit of thefirst PLMN; and a second base station central unit of the second PLMN.At 5440, the base station distributed unit may transmit the radioresource control message to the at least one base station central unit.

According to an example embodiment, a base station distributed unit maytransmit to a wireless device, at least one system information blockindicating a plurality of public land mobile networks (PLMNs). A radioresource control message may be received from the wireless device. Theradio resource control message may indicate a selected PLMN from theplurality of PLMNs. A base station central unit may be selected, basedon the selected PLMN, from a plurality of base station central units.the base station central unit may transmit the radio resource controlmessage. According to an example embodiment, the base station centralunit may be associated with the selected PLMN.

FIG. 55 is an example flow diagram as per an aspect of an embodiment ofthe present disclosure. At 5510, a base station distributed unit maytransmit at least one system information block to a wireless device. Theat least one system information block may indicate a plurality ofnetworks. At 5520, a radio resource control message may be received fromthe wireless device. The radio resource control message may indicate aselected network from the plurality of networks. At 5530, a base stationcentral unit may be selected, based on the selected network, from aplurality of base station central units. At 5540, the base stationcentral unit may transmit the radio resource control message. Accordingto an example embodiment, the base station central unit may beassociated with the selected network.

In this disclosure, “a” and “an” and similar phrases are to beinterpreted as “at least one” and “one or more.” Similarly, any termthat ends with the suffix “(s)” is to be interpreted as “at least one”and “one or more.” In this disclosure, the term “may” is to beinterpreted as “may, for example.” In other words, the term “may” isindicative that the phrase following the term “may” is an example of oneof a multitude of suitable possibilities that may, or may not, beemployed to one or more of the various embodiments.

If A and B are sets and every element of A is also an element of B, A iscalled a subset of B. In this specification, only non-empty sets andsubsets are considered. For example, possible subsets of B={cell1,cell2} are: {cell1}, {cell2}, and {cell1, cell2}. The phrase “based on”(or equally “based at least on”) is indicative that the phrase followingthe term “based on” is an example of one of a multitude of suitablepossibilities that may, or may not, be employed to one or more of thevarious embodiments. The phrase “in response to” (or equally “inresponse at least to”) is indicative that the phrase following thephrase “in response to” is an example of one of a multitude of suitablepossibilities that may, or may not, be employed to one or more of thevarious embodiments. The phrase “depending on” (or equally “depending atleast to”) is indicative that the phrase following the phrase “dependingon” is an example of one of a multitude of suitable possibilities thatmay, or may not, be employed to one or more of the various embodiments.The phrase “employing/using” (or equally “employing/using at least”) isindicative that the phrase following the phrase “employing/using” is anexample of one of a multitude of suitable possibilities that may, or maynot, be employed to one or more of the various embodiments.

The term configured may relate to the capacity of a device whether thedevice is in an operational or non-operational state. Configured mayalso refer to specific settings in a device that effect the operationalcharacteristics of the device whether the device is in an operational ornon-operational state. In other words, the hardware, software, firmware,registers, memory values, and/or the like may be “configured” within adevice, whether the device is in an operational or nonoperational state,to provide the device with specific characteristics. Terms such as “acontrol message to cause in a device” may mean that a control messagehas parameters that may be used to configure specific characteristics ormay be used to implement certain actions in the device, whether thedevice is in an operational or non-operational state

In this disclosure, various embodiments are disclosed. Limitations,features, and/or elements from the disclosed example embodiments may becombined to create further embodiments within the scope of thedisclosure.

In this disclosure, parameters (or equally called, fields, orInformation elements: IEs) may comprise one or more information objects,and an information object may comprise one or more other objects. Forexample, if parameter (IE) N comprises parameter (IE) M, and parameter(IE) M comprises parameter (IE) K, and parameter (IE) K comprisesparameter (information element) J. Then, for example, N comprises K, andN comprises J. In an example embodiment, when one or more (or at leastone) message(s) comprise a plurality of parameters, it implies that aparameter in the plurality of parameters is in at least one of the oneor more messages, but does not have to be in each of the one or moremessages. In an example embodiment, when one or more (or at least one)message(s) indicate a value, event and/or condition, it implies that thevalue, event and/or condition is indicated by at least one of the one ormore messages, but does not have to be indicated by each of the one ormore messages.

Furthermore, many features presented above are described as beingoptional through the use of “may” or the use of parentheses. For thesake of brevity and legibility, the present disclosure does notexplicitly recite each and every permutation that may be obtained bychoosing from the set of optional features. However, the presentdisclosure is to be interpreted as explicitly disclosing all suchpermutations. For example, a system described as having three optionalfeatures may be embodied in seven different ways, namely with just oneof the three possible features, with any two of the three possiblefeatures or with all three of the three possible features.

Many of the elements described in the disclosed embodiments may beimplemented as modules. A module is defined here as an element thatperforms a defined function and has a defined interface to otherelements. The modules described in this disclosure may be implemented inhardware, software in combination with hardware, firmware, wetware (i.e.hardware with a biological element) or a combination thereof, all ofwhich may be behaviorally equivalent. For example, modules may beimplemented as a software routine written in a computer languageconfigured to be executed by a hardware machine (such as C, C++,Fortran, Java, Basic, Matlab or the like) or a modeling/simulationprogram such as Simulink, Stateflow, GNU Octave, or LabVIEWMathScript.Additionally, it may be possible to implement modules using physicalhardware that incorporates discrete or programmable analog, digitaland/or quantum hardware. Examples of programmable hardware comprise:computers, microcontrollers, microprocessors, application-specificintegrated circuits (ASICs); field programmable gate arrays (FPGAs); andcomplex programmable logic devices (CPLDs). Computers, microcontrollersand microprocessors are programmed using languages such as assembly, C,C++ or the like. FPGAs, ASICs and CPLDs are often programmed usinghardware description languages (HDL) such as VHSIC hardware descriptionlanguage (VHDL) or Verilog that configure connections between internalhardware modules with lesser functionality on a programmable device. Theabove mentioned technologies are often used in combination to achievethe result of a functional module.

The disclosure of this patent document incorporates material which issubject to copyright protection. The copyright owner has no objection tothe facsimile reproduction by anyone of the patent document or thepatent disclosure, as it appears in the Patent and Trademark Officepatent file or records, for the limited purposes required by law, butotherwise reserves all copyright rights whatsoever.

While various embodiments have been described above, it should beunderstood that they have been presented by way of example, and notlimitation. It will be apparent to persons skilled in the relevantart(s) that various changes in form and detail can be made thereinwithout departing from the scope. In fact, after reading the abovedescription, it will be apparent to one skilled in the relevant art(s)how to implement alternative embodiments. Thus, the present embodimentsshould not be limited by any of the above described exemplaryembodiments.

In addition, it should be understood that any figures which highlightthe functionality and advantages, are presented for example purposesonly. The disclosed architecture is sufficiently flexible andconfigurable, such that it may be utilized in ways other than thatshown. For example, the actions listed in any flowchart may bere-ordered or only optionally used in some embodiments.

Further, the purpose of the Abstract of the Disclosure is to enable theU.S. Patent and Trademark Office and the public generally, andespecially the scientists, engineers and practitioners in the art whoare not familiar with patent or legal terms or phraseology, to determinequickly from a cursory inspection the nature and essence of thetechnical disclosure of the application. The Abstract of the Disclosureis not intended to be limiting as to the scope in any way.

Finally, it is the applicant's intent that only claims that include theexpress language “means for” or “step for” be interpreted under 35U.S.C. 112. Claims that do not expressly include the phrase “means for”or “step for” are not to be interpreted under 35 U.S.C. 112.

What is claimed is:
 1. A method comprising: receiving, by a base stationdistributed unit from a first base station central unit, at least onemessage comprising: one or more first configuration parametersassociated with the first base station central unit; and one or moresecond configuration parameters associated with a second base stationcentral unit; and transmitting, by the base station distributed unit,the one or more first configuration parameters and the one or moresecond configuration parameters, wherein: the first base station centralunit is associated with a first public land mobile network (PLMN), andthe one or more first configuration parameters comprise a first PLMNidentifier of the first PLMN; and the second base station central unitis associated with a second PLMN, and the one or more secondconfiguration parameters comprise a second PLMN identifier of the secondPLMN, and wherein the first PLMN and the second PLMN are different fromeach other.
 2. The method of claim 1, wherein the at least one messagecomprises: an F1 setup response message; a base station central unitconfiguration update message; or a base station distributed unitconfiguration update acknowledge message.
 3. The method of claim 1,wherein the transmitting the one or more first configuration parametersand the one or more second configuration parameters comprisestransmitting, by the base station distributed unit to a wireless device,at least one system information block (SIB) comprising the one or morefirst configuration parameters and the one or more second configurationparameters.
 4. The method of claim 3, wherein the at least one SIBcomprises: a first SIB comprising the first PLMN identifier; and asecond SIB comprising the second PLMN identifier.
 5. The method of claim3, wherein the at least one SIB comprises cell parameters for at leastone of a first public land mobile network (PLMN) or a second PLMN, thecell parameters comprising at least one of: a cell identifier of a cellthat transmits the at least one SIB; a closed subscriber groupidentifier of the cell; a first cell identifier of the cell, wherein thefirst cell identifier is associated with the first PLMN; a second cellidentifier of the cell, wherein the second cell identifier is associatedwith the second PLMN; a first closed subscriber group identifier of thecell, wherein the first closed subscriber group identifier is associatedwith the first PLMN; a second closed subscriber group identifier of thecell, wherein the second closed subscriber group identifier isassociated with the second PLMN; a first base station central unitidentifier of the first base station central unit; a second base stationcentral unit identifier of the first base station central unit; a firstbase station identifier of a first base station associated with thefirst base station central unit; or a second base station identifier ofa second base station associated with the second base station centralunit.
 6. The method of claim 1, further comprising: receiving, by thebase station distributed unit from a wireless device, a radio resourcecontrol message that is based on at least one of the one or more firstconfiguration parameters or the one or more second configurationparameters; and configuring, by the base station distributed unit, radioresources for the wireless device based on the radio resource controlmessage.
 7. The method of claim 1, further comprising: receiving, by thebase station distributed unit, at least one packet from at least one ofthe first base station central unit or the second base station centralunit; and transmitting, by the base station distributed unit, the atleast one packet to a wireless device.
 8. The method of claim 1,wherein: a first base station comprises the first base station centralunit and the base station distributed unit; and the first base stationfurther comprises the second base station central unit.
 9. The method ofclaim 1, wherein: a first base station comprises the first base stationcentral unit and the base station distributed unit; and a second basestation comprises the second base station central unit and the basestation distributed unit.
 10. The method of claim 1, further comprisingreceiving, by the first base station central unit from the second basestation central unit, at least one message comprising the one or moresecond configuration parameters associated with the second base stationcentral unit, wherein the base station distributed unit receives fromthe first base station central unit the at least one message comprisingone or more first configuration parameters and one or more secondconfiguration parameters.
 11. A method comprising: receiving, by a firstbase station central unit, one or more second configuration parametersassociated with a second base station central unit; and sending, by thefirst base station central unit to a base station distributed unit, atleast one message comprising: one or more first configuration parametersassociated with the first base station central unit; and the one or moresecond configuration parameters associated with the second base stationcentral unit, wherein: the first base station central unit is associatedwith a first public land mobile network (PLMN), and the one or morefirst configuration parameters comprise a first PLMN identifier of thefirst PLMN; and the second base station central unit is associated witha second PLMN, and the one or more second configuration parameterscomprise a second PLMN identifier of the second PLMN, and wherein thefirst PLMN and the second PLMN are different from each other.
 12. Themethod of claim 11, further comprising: receiving, by the first basestation central unit, at least one packet for a wireless device; andsending, by the first base station central unit, the at least one packetto the base station distributed unit.
 13. The method of claim 11,wherein the at least one message comprises: an F1 setup responsemessage; a base station central unit configuration update message; or abase station distributed unit configuration update acknowledge message.14. The method of claim 11, wherein a first base station comprises thefirst base station central unit and the base station distributed unit,and: the first base station further comprises the second base stationcentral unit; or a second base station comprises the second base stationcentral unit and the base station distributed unit.
 15. A methodcomprising: receiving, by a first base station central unit, one or moresecond configuration parameters associated with a second base stationcentral unit; and receiving, by a base station distributed unit from thefirst base station central unit, at least one message comprising: one ormore first configuration parameters associated with the first basestation central unit; and the one or more second configurationparameters associated with a second base station central unit; andtransmitting, by the base station distributed unit, the one or morefirst configuration parameters and the one or more second configurationparameters, wherein: the first base station central unit is associatedwith a first public land mobile network (PLMN), and the one or morefirst configuration parameters comprise a first PLMN identifier of thefirst PLMN; and the second base station central unit is associated witha second PLMN, and the one or more second configuration parameterscomprise a second PLMN identifier of the second PLMN, and wherein thefirst PLMN and the second PLMN are different from each other.
 16. Themethod of claim 15, wherein the at least one message comprises: an F1setup response message; a base station central unit configuration updatemessage; or a base station distributed unit configuration updateacknowledge message.
 17. The method of claim 15, wherein thetransmitting the one or more first configuration parameters and the oneor more second configuration parameters comprises transmitting, by thebase station distributed unit to a wireless device, at least one systeminformation block (SIB) comprising the one or more first configurationparameters and the one or more second configuration parameters.
 18. Themethod of claim 17, wherein the at least one SIB comprises: a first SIBcomprising the first PLMN identifier; and a second SIB comprising thesecond PLMN identifier.